2004
DOI: 10.17487/rfc3837
|View full text |Cite
|
Sign up to set email alerts
|

Security Threats and Risks for Open Pluggable Edge Services (OPES)

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4

Citation Types

0
4
0

Year Published

2004
2004
2007
2007

Publication Types

Select...
6

Relationship

3
3

Authors

Journals

citations
Cited by 7 publications
(4 citation statements)
references
References 4 publications
0
4
0
Order By: Relevance
“…General security threats of OPES are described in Security Threats for OPES [8] Section 3.3 ("Compatibility with Cryptographic Protection Mechanisms") mentions that an OPES system could eventually deal with cryptographic keys. This raises security issues (such as availability and storage of cryptographic keys) that must be addressed by the implementer.…”
Section: Security Considerationsmentioning
confidence: 99%
“…General security threats of OPES are described in Security Threats for OPES [8] Section 3.3 ("Compatibility with Cryptographic Protection Mechanisms") mentions that an OPES system could eventually deal with cryptographic keys. This raises security issues (such as availability and storage of cryptographic keys) that must be addressed by the implementer.…”
Section: Security Considerationsmentioning
confidence: 99%
“…There are security and privacy issues that relate to data consumer application, callout protocol, and the OPES flow. In [6], there is an analysis of the threats against OPES entities.…”
Section: Security Considerationsmentioning
confidence: 99%
“…Security Considerations Security considerations for OPES are documented in [4]. Policy and authorization issues are documented in [3].…”
Section: Iana Considerationsmentioning
confidence: 99%
“…Policy can be used to indicate what trace information can be expected from a peer entity. Other application level related security concerns can be found in [4].…”
Section: Tracing Security Considerationsmentioning
confidence: 99%