statement_id
stringlengths
26
83
source
stringclasses
6 values
subject_id
stringlengths
3
70
subject_label
stringlengths
0
250
subject_description
stringlengths
0
250
subject_instance_of_ids
stringlengths
0
139
subject_instance_of_labels
stringlengths
0
310
property_id
stringlengths
2
6
property_label
stringlengths
0
80
value_id
stringlengths
1
1.9k
value_label
stringlengths
0
1.9k
value_type
stringclasses
8 values
qualifier_property_id
stringclasses
948 values
qualifier_property_label
stringclasses
947 values
qualifier_value_id
stringlengths
0
686
qualifier_value_label
stringlengths
0
205
STD:IETF:RFC9752$579afe877e5d
IETF
STD:IETF:RFC9752
Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE
PROPOSED STANDARD
Q212971
Request for Comments
P50
author
C. Li
C. Li
string
STD:IETF:RFC9752$936085e52441
IETF
STD:IETF:RFC9752
Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE
PROPOSED STANDARD
Q212971
Request for Comments
P50
author
S. Sidor
S. Sidor
string
STD:IETF:RFC9752$a688ebd76a87
IETF
STD:IETF:RFC9752
Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE
PROPOSED STANDARD
Q212971
Request for Comments
P1476
title
Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE
Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE
monolingualtext
STD:IETF:RFC9752$ac9f61bb9244
IETF
STD:IETF:RFC9752
Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE
PROPOSED STANDARD
Q212971
Request for Comments
P31
instance of
Q212971
Request for Comments
wikibase-item
STD:IETF:RFC9752$bc352ba09001
IETF
STD:IETF:RFC9752
Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE
PROPOSED STANDARD
Q212971
Request for Comments
P50
author
S. Sivabalan
S. Sivabalan
string
STD:IETF:RFC9752$bd31ddda93be
IETF
STD:IETF:RFC9752
Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE
PROPOSED STANDARD
Q212971
Request for Comments
P50
author
Z. Ali
Z. Ali
string
STD:IETF:RFC9752$c0d88594485b
IETF
STD:IETF:RFC9752
Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE
PROPOSED STANDARD
Q212971
Request for Comments
P407
language of work or name
en
English
wikibase-item
STD:IETF:RFC9752$d5532069506f
IETF
STD:IETF:RFC9752
Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE
PROPOSED STANDARD
Q212971
Request for Comments
P5008
on focus list of Wikimedia project (status)
PROPOSED STANDARD
PROPOSED STANDARD
string
STD:IETF:RFC9752$d5532069506f
IETF
STD:IETF:RFC9752
Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE
PROPOSED STANDARD
Q212971
Request for Comments
P5008
on focus list of Wikimedia project (status)
PROPOSED STANDARD
PROPOSED STANDARD
string
STD:IETF:RFC9752$dee6791f689c
IETF
STD:IETF:RFC9752
Conveying Vendor-Specific Information in the Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE
PROPOSED STANDARD
Q212971
Request for Comments
P577
publication date
2025-01
2025-01
time
STD:IETF:RFC9753$0321785a8a23
IETF
STD:IETF:RFC9753
Extension for Stateful PCE to Allow Optional Processing of Path Computation Element Communication Protocol (PCEP) Objects
PROPOSED STANDARD
Q212971
Request for Comments
P50
author
S. Litkowski
S. Litkowski
string
STD:IETF:RFC9753$1aa2d9fe778a
IETF
STD:IETF:RFC9753
Extension for Stateful PCE to Allow Optional Processing of Path Computation Element Communication Protocol (PCEP) Objects
PROPOSED STANDARD
Q212971
Request for Comments
P50
author
C. Li
C. Li
string
STD:IETF:RFC9753$281fada87cee
IETF
STD:IETF:RFC9753
Extension for Stateful PCE to Allow Optional Processing of Path Computation Element Communication Protocol (PCEP) Objects
PROPOSED STANDARD
Q212971
Request for Comments
P407
language of work or name
en
English
wikibase-item
STD:IETF:RFC9753$6660ddd9ecdd
IETF
STD:IETF:RFC9753
Extension for Stateful PCE to Allow Optional Processing of Path Computation Element Communication Protocol (PCEP) Objects
PROPOSED STANDARD
Q212971
Request for Comments
P953
full work available at URL
https://www.rfc-editor.org/rfc/rfc9753
https://www.rfc-editor.org/rfc/rfc9753
url
STD:IETF:RFC9753$716a4123cc3c
IETF
STD:IETF:RFC9753
Extension for Stateful PCE to Allow Optional Processing of Path Computation Element Communication Protocol (PCEP) Objects
PROPOSED STANDARD
Q212971
Request for Comments
P577
publication date
2025-01
2025-01
time
STD:IETF:RFC9753$836ac62137c4
IETF
STD:IETF:RFC9753
Extension for Stateful PCE to Allow Optional Processing of Path Computation Element Communication Protocol (PCEP) Objects
PROPOSED STANDARD
Q212971
Request for Comments
P50
author
H. Zheng
H. Zheng
string
STD:IETF:RFC9753$8bcd32fceebb
IETF
STD:IETF:RFC9753
Extension for Stateful PCE to Allow Optional Processing of Path Computation Element Communication Protocol (PCEP) Objects
PROPOSED STANDARD
Q212971
Request for Comments
P5008
on focus list of Wikimedia project (status)
PROPOSED STANDARD
PROPOSED STANDARD
string
STD:IETF:RFC9753$8bcd32fceebb
IETF
STD:IETF:RFC9753
Extension for Stateful PCE to Allow Optional Processing of Path Computation Element Communication Protocol (PCEP) Objects
PROPOSED STANDARD
Q212971
Request for Comments
P5008
on focus list of Wikimedia project (status)
PROPOSED STANDARD
PROPOSED STANDARD
string
STD:IETF:RFC9753$aed4c29185a2
IETF
STD:IETF:RFC9753
Extension for Stateful PCE to Allow Optional Processing of Path Computation Element Communication Protocol (PCEP) Objects
PROPOSED STANDARD
Q212971
Request for Comments
P1683
quotation (abstract)
This document introduces a mechanism to mark some of the Path Computation Element Communication Protocol (PCEP) objects as optional during PCEP message exchange, so the stateful Path Computation Element (PCE) model can relax some constraints during path computation and setup. This document introduces this relaxation t...
This document introduces a mechanism to mark some of the Path Computation Element Communication Protocol (PCEP) objects as optional during PCEP message exchange, so the stateful Path Computation Element (PCE) model can relax some constraints during path computation and setup. This document introduces this relaxation t...
monolingualtext
STD:IETF:RFC9753$b53c91578931
IETF
STD:IETF:RFC9753
Extension for Stateful PCE to Allow Optional Processing of Path Computation Element Communication Protocol (PCEP) Objects
PROPOSED STANDARD
Q212971
Request for Comments
P1476
title
Extension for Stateful PCE to Allow Optional Processing of Path Computation Element Communication Protocol (PCEP) Objects
Extension for Stateful PCE to Allow Optional Processing of Path Computation Element Communication Protocol (PCEP) Objects
monolingualtext
STD:IETF:RFC9753$cd7e14e65a37
IETF
STD:IETF:RFC9753
Extension for Stateful PCE to Allow Optional Processing of Path Computation Element Communication Protocol (PCEP) Objects
PROPOSED STANDARD
Q212971
Request for Comments
P31
instance of
Q212971
Request for Comments
wikibase-item
STD:IETF:RFC9754$05c0f9486466
IETF
STD:IETF:RFC9754
Extensions for Opening and Delegating Files in NFSv4.2
PROPOSED STANDARD
Q212971
Request for Comments
P1683
quotation (abstract)
The Network File System v4 (NFSv4) allows a client to both open a file and be granted a delegation of that file. This delegation provides the client the right to authoritatively cache metadata on the file locally. This document presents several extensions for both opening the file and delegating it to the client. Th...
The Network File System v4 (NFSv4) allows a client to both open a file and be granted a delegation of that file. This delegation provides the client the right to authoritatively cache metadata on the file locally. This document presents several extensions for both opening the file and delegating it to the client. Th...
monolingualtext
STD:IETF:RFC9754$251cb73d1a33
IETF
STD:IETF:RFC9754
Extensions for Opening and Delegating Files in NFSv4.2
PROPOSED STANDARD
Q212971
Request for Comments
P953
full work available at URL
https://www.rfc-editor.org/rfc/rfc9754
https://www.rfc-editor.org/rfc/rfc9754
url
STD:IETF:RFC9754$680c32f1ffde
IETF
STD:IETF:RFC9754
Extensions for Opening and Delegating Files in NFSv4.2
PROPOSED STANDARD
Q212971
Request for Comments
P577
publication date
2025-01
2025-01
time
STD:IETF:RFC9754$93a49fd929cc
IETF
STD:IETF:RFC9754
Extensions for Opening and Delegating Files in NFSv4.2
PROPOSED STANDARD
Q212971
Request for Comments
P407
language of work or name
en
English
wikibase-item
STD:IETF:RFC9754$a26faf0bb425
IETF
STD:IETF:RFC9754
Extensions for Opening and Delegating Files in NFSv4.2
PROPOSED STANDARD
Q212971
Request for Comments
P1476
title
Extensions for Opening and Delegating Files in NFSv4.2
Extensions for Opening and Delegating Files in NFSv4.2
monolingualtext
STD:IETF:RFC9754$c1b8ae093491
IETF
STD:IETF:RFC9754
Extensions for Opening and Delegating Files in NFSv4.2
PROPOSED STANDARD
Q212971
Request for Comments
P31
instance of
Q212971
Request for Comments
wikibase-item
STD:IETF:RFC9754$d452911a8f76
IETF
STD:IETF:RFC9754
Extensions for Opening and Delegating Files in NFSv4.2
PROPOSED STANDARD
Q212971
Request for Comments
P50
author
T. Haynes
T. Haynes
string
STD:IETF:RFC9754$d810e6001821
IETF
STD:IETF:RFC9754
Extensions for Opening and Delegating Files in NFSv4.2
PROPOSED STANDARD
Q212971
Request for Comments
P50
author
T. Myklebust
T. Myklebust
string
STD:IETF:RFC9754$e187f0bd6f18
IETF
STD:IETF:RFC9754
Extensions for Opening and Delegating Files in NFSv4.2
PROPOSED STANDARD
Q212971
Request for Comments
P5008
on focus list of Wikimedia project (status)
PROPOSED STANDARD
PROPOSED STANDARD
string
STD:IETF:RFC9754$e187f0bd6f18
IETF
STD:IETF:RFC9754
Extensions for Opening and Delegating Files in NFSv4.2
PROPOSED STANDARD
Q212971
Request for Comments
P5008
on focus list of Wikimedia project (status)
PROPOSED STANDARD
PROPOSED STANDARD
string
STD:IETF:RFC9755$0fd959cf1205
IETF
STD:IETF:RFC9755
IMAP Support for UTF-8
PROPOSED STANDARD
Q212971
Request for Comments
P50
author
P. Resnick
P. Resnick
string
STD:IETF:RFC9755$19e64ffe9b47
IETF
STD:IETF:RFC9755
IMAP Support for UTF-8
PROPOSED STANDARD
Q212971
Request for Comments
P50
author
J. Yao
J. Yao
string
STD:IETF:RFC9755$4334baad8716
IETF
STD:IETF:RFC9755
IMAP Support for UTF-8
PROPOSED STANDARD
Q212971
Request for Comments
P50
author
A. Gulbrandsen
A. Gulbrandsen
string
STD:IETF:RFC9755$592bac6317a0
IETF
STD:IETF:RFC9755
IMAP Support for UTF-8
PROPOSED STANDARD
Q212971
Request for Comments
P1476
title
IMAP Support for UTF-8
IMAP Support for UTF-8
monolingualtext
STD:IETF:RFC9755$5ada4069a319
IETF
STD:IETF:RFC9755
IMAP Support for UTF-8
PROPOSED STANDARD
Q212971
Request for Comments
P1683
quotation (abstract)
This specification extends the Internet Message Access Protocol, specifically IMAP4rev1 (RFC 3501), to support UTF-8 encoded international characters in user names, mail addresses, and message headers. This specification replaces RFC 6855. This specification does not extend IMAP4rev2 (RFC 9051), since that protocol i...
This specification extends the Internet Message Access Protocol, specifically IMAP4rev1 (RFC 3501), to support UTF-8 encoded international characters in user names, mail addresses, and message headers. This specification replaces RFC 6855. This specification does not extend IMAP4rev2 (RFC 9051), since that protocol i...
monolingualtext
STD:IETF:RFC9755$5f1ea0df6fb4
IETF
STD:IETF:RFC9755
IMAP Support for UTF-8
PROPOSED STANDARD
Q212971
Request for Comments
P155
follows
STD:IETF:RFC6855
RFC6855
wikibase-item
STD:IETF:RFC9755$9a324cdaa77c
IETF
STD:IETF:RFC9755
IMAP Support for UTF-8
PROPOSED STANDARD
Q212971
Request for Comments
P577
publication date
2025-01
2025-01
time
STD:IETF:RFC9755$9c0523b38504
IETF
STD:IETF:RFC9755
IMAP Support for UTF-8
PROPOSED STANDARD
Q212971
Request for Comments
P953
full work available at URL
https://www.rfc-editor.org/rfc/rfc9755
https://www.rfc-editor.org/rfc/rfc9755
url
STD:IETF:RFC9755$ad48b2ab109a
IETF
STD:IETF:RFC9755
IMAP Support for UTF-8
PROPOSED STANDARD
Q212971
Request for Comments
P31
instance of
Q212971
Request for Comments
wikibase-item
STD:IETF:RFC9755$b721e1531002
IETF
STD:IETF:RFC9755
IMAP Support for UTF-8
PROPOSED STANDARD
Q212971
Request for Comments
P5008
on focus list of Wikimedia project (status)
PROPOSED STANDARD
PROPOSED STANDARD
string
STD:IETF:RFC9755$b721e1531002
IETF
STD:IETF:RFC9755
IMAP Support for UTF-8
PROPOSED STANDARD
Q212971
Request for Comments
P5008
on focus list of Wikimedia project (status)
PROPOSED STANDARD
PROPOSED STANDARD
string
STD:IETF:RFC9755$f3e746a45b1a
IETF
STD:IETF:RFC9755
IMAP Support for UTF-8
PROPOSED STANDARD
Q212971
Request for Comments
P407
language of work or name
en
English
wikibase-item
STD:IETF:RFC9756$35d9f7c56071
IETF
STD:IETF:RFC9756
Update to the IANA Path Communication Element Protocol (PCEP) Numbers Registration Procedures and the Allowance of Experimental Error Codes
PROPOSED STANDARD
Q212971
Request for Comments
P31
instance of
Q212971
Request for Comments
wikibase-item
STD:IETF:RFC9756$624bede194a6
IETF
STD:IETF:RFC9756
Update to the IANA Path Communication Element Protocol (PCEP) Numbers Registration Procedures and the Allowance of Experimental Error Codes
PROPOSED STANDARD
Q212971
Request for Comments
P50
author
D. Dhody
D. Dhody
string
STD:IETF:RFC9756$6e2789984e42
IETF
STD:IETF:RFC9756
Update to the IANA Path Communication Element Protocol (PCEP) Numbers Registration Procedures and the Allowance of Experimental Error Codes
PROPOSED STANDARD
Q212971
Request for Comments
P577
publication date
2025-01
2025-01
time
STD:IETF:RFC9756$9358ba7373b9
IETF
STD:IETF:RFC9756
Update to the IANA Path Communication Element Protocol (PCEP) Numbers Registration Procedures and the Allowance of Experimental Error Codes
PROPOSED STANDARD
Q212971
Request for Comments
P1683
quotation (abstract)
This document updates the registration procedure within the IANA "Path Computation Element Protocol (PCEP) Numbers" registry group. This specification changes some of the registries with Standards Action to IETF Review as defined in RFC 8126 and thus updates RFCs 8231, 8233, 8281, 8623, 8664, 8685, 8697, 8733, 8745, 87...
This document updates the registration procedure within the IANA "Path Computation Element Protocol (PCEP) Numbers" registry group. This specification changes some of the registries with Standards Action to IETF Review as defined in RFC 8126 and thus updates RFCs 8231, 8233, 8281, 8623, 8664, 8685, 8697, 8733, 8745, 87...
monolingualtext
STD:IETF:RFC9756$95d508648450
IETF
STD:IETF:RFC9756
Update to the IANA Path Communication Element Protocol (PCEP) Numbers Registration Procedures and the Allowance of Experimental Error Codes
PROPOSED STANDARD
Q212971
Request for Comments
P5008
on focus list of Wikimedia project (status)
PROPOSED STANDARD
PROPOSED STANDARD
string
STD:IETF:RFC9756$95d508648450
IETF
STD:IETF:RFC9756
Update to the IANA Path Communication Element Protocol (PCEP) Numbers Registration Procedures and the Allowance of Experimental Error Codes
PROPOSED STANDARD
Q212971
Request for Comments
P5008
on focus list of Wikimedia project (status)
PROPOSED STANDARD
PROPOSED STANDARD
string
STD:IETF:RFC9756$b6aa6bef8df4
IETF
STD:IETF:RFC9756
Update to the IANA Path Communication Element Protocol (PCEP) Numbers Registration Procedures and the Allowance of Experimental Error Codes
PROPOSED STANDARD
Q212971
Request for Comments
P407
language of work or name
en
English
wikibase-item
STD:IETF:RFC9756$de407602f861
IETF
STD:IETF:RFC9756
Update to the IANA Path Communication Element Protocol (PCEP) Numbers Registration Procedures and the Allowance of Experimental Error Codes
PROPOSED STANDARD
Q212971
Request for Comments
P1476
title
Update to the IANA Path Communication Element Protocol (PCEP) Numbers Registration Procedures and the Allowance of Experimental Error Codes
Update to the IANA Path Communication Element Protocol (PCEP) Numbers Registration Procedures and the Allowance of Experimental Error Codes
monolingualtext
STD:IETF:RFC9756$efb5261c4a86
IETF
STD:IETF:RFC9756
Update to the IANA Path Communication Element Protocol (PCEP) Numbers Registration Procedures and the Allowance of Experimental Error Codes
PROPOSED STANDARD
Q212971
Request for Comments
P50
author
A. Farrel
A. Farrel
string
STD:IETF:RFC9756$f47d273724f9
IETF
STD:IETF:RFC9756
Update to the IANA Path Communication Element Protocol (PCEP) Numbers Registration Procedures and the Allowance of Experimental Error Codes
PROPOSED STANDARD
Q212971
Request for Comments
P953
full work available at URL
https://www.rfc-editor.org/rfc/rfc9756
https://www.rfc-editor.org/rfc/rfc9756
url
STD:IETF:RFC9757$11a2a23befc7
IETF
STD:IETF:RFC9757
Path Computation Element Communication Protocol (PCEP) Extensions for Native IP Networks
EXPERIMENTAL
Q212971
Request for Comments
P1476
title
Path Computation Element Communication Protocol (PCEP) Extensions for Native IP Networks
Path Computation Element Communication Protocol (PCEP) Extensions for Native IP Networks
monolingualtext
STD:IETF:RFC9757$4377eb1e4683
IETF
STD:IETF:RFC9757
Path Computation Element Communication Protocol (PCEP) Extensions for Native IP Networks
EXPERIMENTAL
Q212971
Request for Comments
P50
author
A. Wang
A. Wang
string
STD:IETF:RFC9757$4f049f0f332e
IETF
STD:IETF:RFC9757
Path Computation Element Communication Protocol (PCEP) Extensions for Native IP Networks
EXPERIMENTAL
Q212971
Request for Comments
P5008
on focus list of Wikimedia project (status)
EXPERIMENTAL
EXPERIMENTAL
string
STD:IETF:RFC9757$4f049f0f332e
IETF
STD:IETF:RFC9757
Path Computation Element Communication Protocol (PCEP) Extensions for Native IP Networks
EXPERIMENTAL
Q212971
Request for Comments
P5008
on focus list of Wikimedia project (status)
EXPERIMENTAL
EXPERIMENTAL
string
STD:IETF:RFC9757$57ad1e6d0545
IETF
STD:IETF:RFC9757
Path Computation Element Communication Protocol (PCEP) Extensions for Native IP Networks
EXPERIMENTAL
Q212971
Request for Comments
P50
author
C. Zhu
C. Zhu
string
STD:IETF:RFC9757$8e85caf5a839
IETF
STD:IETF:RFC9757
Path Computation Element Communication Protocol (PCEP) Extensions for Native IP Networks
EXPERIMENTAL
Q212971
Request for Comments
P577
publication date
2025-01
2025-01
time
STD:IETF:RFC9757$c4f80242bf01
IETF
STD:IETF:RFC9757
Path Computation Element Communication Protocol (PCEP) Extensions for Native IP Networks
EXPERIMENTAL
Q212971
Request for Comments
P31
instance of
Q212971
Request for Comments
wikibase-item
STD:IETF:RFC9757$d8b6285e436e
IETF
STD:IETF:RFC9757
Path Computation Element Communication Protocol (PCEP) Extensions for Native IP Networks
EXPERIMENTAL
Q212971
Request for Comments
P50
author
S. Fang
S. Fang
string
STD:IETF:RFC9757$db3bffe03d53
IETF
STD:IETF:RFC9757
Path Computation Element Communication Protocol (PCEP) Extensions for Native IP Networks
EXPERIMENTAL
Q212971
Request for Comments
P50
author
B. Khasanov
B. Khasanov
string
STD:IETF:RFC9757$ee1d59bd995f
IETF
STD:IETF:RFC9757
Path Computation Element Communication Protocol (PCEP) Extensions for Native IP Networks
EXPERIMENTAL
Q212971
Request for Comments
P953
full work available at URL
https://www.rfc-editor.org/rfc/rfc9757
https://www.rfc-editor.org/rfc/rfc9757
url
STD:IETF:RFC9757$f3e34067c0ed
IETF
STD:IETF:RFC9757
Path Computation Element Communication Protocol (PCEP) Extensions for Native IP Networks
EXPERIMENTAL
Q212971
Request for Comments
P1683
quotation (abstract)
This document introduces extensions to the Path Computation Element Communication Protocol (PCEP) to support path computation in Native IP networks through a PCE-based central control mechanism known as Centralized Control Dynamic Routing (CCDR). These extensions empower a PCE to calculate and manage paths specificall...
This document introduces extensions to the Path Computation Element Communication Protocol (PCEP) to support path computation in Native IP networks through a PCE-based central control mechanism known as Centralized Control Dynamic Routing (CCDR). These extensions empower a PCE to calculate and manage paths specificall...
monolingualtext
STD:IETF:RFC9757$fd1d8fd6fdae
IETF
STD:IETF:RFC9757
Path Computation Element Communication Protocol (PCEP) Extensions for Native IP Networks
EXPERIMENTAL
Q212971
Request for Comments
P407
language of work or name
en
English
wikibase-item
STD:IETF:RFC9758$1dac2c59f5bb
IETF
STD:IETF:RFC9758
Updates to the 'ipn' URI Scheme
PROPOSED STANDARD
Q212971
Request for Comments
P50
author
E. Birrane III
E. Birrane III
string
STD:IETF:RFC9758$2051e866f829
IETF
STD:IETF:RFC9758
Updates to the 'ipn' URI Scheme
PROPOSED STANDARD
Q212971
Request for Comments
P407
language of work or name
en
English
wikibase-item
STD:IETF:RFC9758$44cf50b031fa
IETF
STD:IETF:RFC9758
Updates to the 'ipn' URI Scheme
PROPOSED STANDARD
Q212971
Request for Comments
P31
instance of
Q212971
Request for Comments
wikibase-item
STD:IETF:RFC9758$6fa8a42579b2
IETF
STD:IETF:RFC9758
Updates to the 'ipn' URI Scheme
PROPOSED STANDARD
Q212971
Request for Comments
P50
author
R. Taylor
R. Taylor
string
STD:IETF:RFC9758$6fbbeec52409
IETF
STD:IETF:RFC9758
Updates to the 'ipn' URI Scheme
PROPOSED STANDARD
Q212971
Request for Comments
P577
publication date
2025-01
2025-01
time
STD:IETF:RFC9758$902b627d115a
IETF
STD:IETF:RFC9758
Updates to the 'ipn' URI Scheme
PROPOSED STANDARD
Q212971
Request for Comments
P5008
on focus list of Wikimedia project (status)
PROPOSED STANDARD
PROPOSED STANDARD
string
STD:IETF:RFC9758$902b627d115a
IETF
STD:IETF:RFC9758
Updates to the 'ipn' URI Scheme
PROPOSED STANDARD
Q212971
Request for Comments
P5008
on focus list of Wikimedia project (status)
PROPOSED STANDARD
PROPOSED STANDARD
string
STD:IETF:RFC9758$aee27a24dba1
IETF
STD:IETF:RFC9758
Updates to the 'ipn' URI Scheme
PROPOSED STANDARD
Q212971
Request for Comments
P1683
quotation (abstract)
This document updates the specification of the 'ipn' URI scheme previously defined in RFC 6260 and the IANA registries established in RFC 7116. It also updates the rules for the encoding and decoding of these URIs when used as an Endpoint Identifier (EID) in the Bundle Protocol version 7 (BPv7) as defined in RFC 9171....
This document updates the specification of the 'ipn' URI scheme previously defined in RFC 6260 and the IANA registries established in RFC 7116. It also updates the rules for the encoding and decoding of these URIs when used as an Endpoint Identifier (EID) in the Bundle Protocol version 7 (BPv7) as defined in RFC 9171....
monolingualtext
STD:IETF:RFC9758$ce3654c91fc5
IETF
STD:IETF:RFC9758
Updates to the 'ipn' URI Scheme
PROPOSED STANDARD
Q212971
Request for Comments
P1476
title
Updates to the 'ipn' URI Scheme
Updates to the 'ipn' URI Scheme
monolingualtext
STD:IETF:RFC9758$fbcd94464070
IETF
STD:IETF:RFC9758
Updates to the 'ipn' URI Scheme
PROPOSED STANDARD
Q212971
Request for Comments
P953
full work available at URL
https://www.rfc-editor.org/rfc/rfc9758
https://www.rfc-editor.org/rfc/rfc9758
url
STD:IETF:RFC9759$1548d10aedef
IETF
STD:IETF:RFC9759
Unified Time Scaling for Temporal Coordination Frameworks
INFORMATIONAL
Q212971
Request for Comments
P1476
title
Unified Time Scaling for Temporal Coordination Frameworks
Unified Time Scaling for Temporal Coordination Frameworks
monolingualtext
STD:IETF:RFC9759$38c03bb5c773
IETF
STD:IETF:RFC9759
Unified Time Scaling for Temporal Coordination Frameworks
INFORMATIONAL
Q212971
Request for Comments
P1683
quotation (abstract)
Estimating time requirements for tasks, both critical and mundane, remains a challenge in engineering, business, and everyday communication. Existing models fail due to inherent unpredictability and inconsistencies in human estimation. This document introduces the Two-Week Principle (TWP), a novel, universally adapta...
Estimating time requirements for tasks, both critical and mundane, remains a challenge in engineering, business, and everyday communication. Existing models fail due to inherent unpredictability and inconsistencies in human estimation. This document introduces the Two-Week Principle (TWP), a novel, universally adapta...
monolingualtext
STD:IETF:RFC9759$4f0f429c2d93
IETF
STD:IETF:RFC9759
Unified Time Scaling for Temporal Coordination Frameworks
INFORMATIONAL
Q212971
Request for Comments
P5008
on focus list of Wikimedia project (status)
INFORMATIONAL
INFORMATIONAL
string
STD:IETF:RFC9759$4f0f429c2d93
IETF
STD:IETF:RFC9759
Unified Time Scaling for Temporal Coordination Frameworks
INFORMATIONAL
Q212971
Request for Comments
P5008
on focus list of Wikimedia project (status)
INFORMATIONAL
INFORMATIONAL
string
STD:IETF:RFC9759$5b0b56a866f9
IETF
STD:IETF:RFC9759
Unified Time Scaling for Temporal Coordination Frameworks
INFORMATIONAL
Q212971
Request for Comments
P577
publication date
2025-01
2025-01
time
STD:IETF:RFC9759$9be4e726ac6f
IETF
STD:IETF:RFC9759
Unified Time Scaling for Temporal Coordination Frameworks
INFORMATIONAL
Q212971
Request for Comments
P31
instance of
Q212971
Request for Comments
wikibase-item
STD:IETF:RFC9759$a2de63700485
IETF
STD:IETF:RFC9759
Unified Time Scaling for Temporal Coordination Frameworks
INFORMATIONAL
Q212971
Request for Comments
P953
full work available at URL
https://www.rfc-editor.org/rfc/rfc9759
https://www.rfc-editor.org/rfc/rfc9759
url
STD:IETF:RFC9759$ac56faad8f06
IETF
STD:IETF:RFC9759
Unified Time Scaling for Temporal Coordination Frameworks
INFORMATIONAL
Q212971
Request for Comments
P407
language of work or name
en
English
wikibase-item
STD:IETF:RFC9759$d6888ac9715c
IETF
STD:IETF:RFC9759
Unified Time Scaling for Temporal Coordination Frameworks
INFORMATIONAL
Q212971
Request for Comments
P50
author
K. Kuhns
K. Kuhns
string
STD:IETF:RFC9760$15fe57e131cf
IETF
STD:IETF:RFC9760
Enterprise Profile for the Precision Time Protocol with Mixed Multicast and Unicast Messages
PROPOSED STANDARD
Q212971
Request for Comments
P407
language of work or name
en
English
wikibase-item
STD:IETF:RFC9760$2c405bb2ff0e
IETF
STD:IETF:RFC9760
Enterprise Profile for the Precision Time Protocol with Mixed Multicast and Unicast Messages
PROPOSED STANDARD
Q212971
Request for Comments
P50
author
D. Arnold
D. Arnold
string
STD:IETF:RFC9760$480ca68cdea4
IETF
STD:IETF:RFC9760
Enterprise Profile for the Precision Time Protocol with Mixed Multicast and Unicast Messages
PROPOSED STANDARD
Q212971
Request for Comments
P5008
on focus list of Wikimedia project (status)
PROPOSED STANDARD
PROPOSED STANDARD
string
STD:IETF:RFC9760$480ca68cdea4
IETF
STD:IETF:RFC9760
Enterprise Profile for the Precision Time Protocol with Mixed Multicast and Unicast Messages
PROPOSED STANDARD
Q212971
Request for Comments
P5008
on focus list of Wikimedia project (status)
PROPOSED STANDARD
PROPOSED STANDARD
string
STD:IETF:RFC9760$69891326691a
IETF
STD:IETF:RFC9760
Enterprise Profile for the Precision Time Protocol with Mixed Multicast and Unicast Messages
PROPOSED STANDARD
Q212971
Request for Comments
P1476
title
Enterprise Profile for the Precision Time Protocol with Mixed Multicast and Unicast Messages
Enterprise Profile for the Precision Time Protocol with Mixed Multicast and Unicast Messages
monolingualtext
STD:IETF:RFC9760$b2c3126a244d
IETF
STD:IETF:RFC9760
Enterprise Profile for the Precision Time Protocol with Mixed Multicast and Unicast Messages
PROPOSED STANDARD
Q212971
Request for Comments
P953
full work available at URL
https://www.rfc-editor.org/rfc/rfc9760
https://www.rfc-editor.org/rfc/rfc9760
url
STD:IETF:RFC9760$e5905fe3c060
IETF
STD:IETF:RFC9760
Enterprise Profile for the Precision Time Protocol with Mixed Multicast and Unicast Messages
PROPOSED STANDARD
Q212971
Request for Comments
P1683
quotation (abstract)
This document describes a Precision Time Protocol (PTP) Profile (IEEE Standard 1588-2019) for use in an IPv4 or IPv6 enterprise information system environment. The PTP Profile uses the End-to-End delay measurement mechanism, allowing both multicast and unicast Delay Request and Delay Response messages.
This document describes a Precision Time Protocol (PTP) Profile (IEEE Standard 1588-2019) for use in an IPv4 or IPv6 enterprise information system environment. The PTP Profile uses the End-to-End delay measurement mechanism, allowing both multicast and unicast Delay Request and Delay Response messages.
monolingualtext
STD:IETF:RFC9760$efa933a59b2e
IETF
STD:IETF:RFC9760
Enterprise Profile for the Precision Time Protocol with Mixed Multicast and Unicast Messages
PROPOSED STANDARD
Q212971
Request for Comments
P31
instance of
Q212971
Request for Comments
wikibase-item
STD:IETF:RFC9760$f09944cd20ec
IETF
STD:IETF:RFC9760
Enterprise Profile for the Precision Time Protocol with Mixed Multicast and Unicast Messages
PROPOSED STANDARD
Q212971
Request for Comments
P50
author
H. Gerstung
H. Gerstung
string
STD:IETF:RFC9760$fae69b2c94b2
IETF
STD:IETF:RFC9760
Enterprise Profile for the Precision Time Protocol with Mixed Multicast and Unicast Messages
PROPOSED STANDARD
Q212971
Request for Comments
P577
publication date
2025-01
2025-01
time
STD:IETF:RFC9761$066f980f22a2
IETF
STD:IETF:RFC9761
Manufacturer Usage Description (MUD) for TLS and DTLS Profiles for Internet of Things (IoT) Devices
PROPOSED STANDARD
Q212971
Request for Comments
P577
publication date
2025-01
2025-01
time
STD:IETF:RFC9761$1cd9e8183670
IETF
STD:IETF:RFC9761
Manufacturer Usage Description (MUD) for TLS and DTLS Profiles for Internet of Things (IoT) Devices
PROPOSED STANDARD
Q212971
Request for Comments
P50
author
T. Reddy.K
T. Reddy.K
string
STD:IETF:RFC9761$259ce9121ab1
IETF
STD:IETF:RFC9761
Manufacturer Usage Description (MUD) for TLS and DTLS Profiles for Internet of Things (IoT) Devices
PROPOSED STANDARD
Q212971
Request for Comments
P407
language of work or name
en
English
wikibase-item
STD:IETF:RFC9761$3eafbee1d3fe
IETF
STD:IETF:RFC9761
Manufacturer Usage Description (MUD) for TLS and DTLS Profiles for Internet of Things (IoT) Devices
PROPOSED STANDARD
Q212971
Request for Comments
P953
full work available at URL
https://www.rfc-editor.org/rfc/rfc9761
https://www.rfc-editor.org/rfc/rfc9761
url
STD:IETF:RFC9761$50f7afcd7795
IETF
STD:IETF:RFC9761
Manufacturer Usage Description (MUD) for TLS and DTLS Profiles for Internet of Things (IoT) Devices
PROPOSED STANDARD
Q212971
Request for Comments
P5008
on focus list of Wikimedia project (status)
PROPOSED STANDARD
PROPOSED STANDARD
string
STD:IETF:RFC9761$50f7afcd7795
IETF
STD:IETF:RFC9761
Manufacturer Usage Description (MUD) for TLS and DTLS Profiles for Internet of Things (IoT) Devices
PROPOSED STANDARD
Q212971
Request for Comments
P5008
on focus list of Wikimedia project (status)
PROPOSED STANDARD
PROPOSED STANDARD
string