2006
DOI: 10.17487/rfc4738
|View full text |Cite
|
Sign up to set email alerts
|

MIKEY-RSA-R: An Additional Mode of Key Distribution in Multimedia Internet KEYing (MIKEY)

Abstract: Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
16
0

Year Published

2006
2006
2016
2016

Publication Types

Select...
5
1

Relationship

0
6

Authors

Journals

citations
Cited by 12 publications
(16 citation statements)
references
References 12 publications
0
16
0
Order By: Relevance
“…The session keys are also encoded in the TICKET payload, but in some use cases (see Section 8) they need to be sent in a separate KEMAC payload. The session information may be sent from the Initiator to the Responder (similar to [RFC3830]) or from the Responder to the Initiator (similar to [RFC4738] The TRANSFER_INIT message MUST always include the Header (HDR), Timestamp (T), and RANDRi payloads.…”
Section: Ticket Transfermentioning
confidence: 99%
See 2 more Smart Citations
“…The session keys are also encoded in the TICKET payload, but in some use cases (see Section 8) they need to be sent in a separate KEMAC payload. The session information may be sent from the Initiator to the Responder (similar to [RFC3830]) or from the Responder to the Initiator (similar to [RFC4738] The TRANSFER_INIT message MUST always include the Header (HDR), Timestamp (T), and RANDRi payloads.…”
Section: Ticket Transfermentioning
confidence: 99%
“…Multiple SP payloads MAY be used both to indicate supported security policies for a specific crypto session (similar to [RFC4738]) and to specify security policies for different crypto sessions (similar to [RFC3830]). …”
Section: Ticket Transfermentioning
confidence: 99%
See 1 more Smart Citation
“…MIKEY in particular describes three key -a symmetric key distribution protocol (MIKEY-PS) based on preshared master keys -a public-key encryption-based key distribution protocol (MIKEY-PK and reverse-mode MIKEY-RSA-R [33]) assuming a public-key infrastructure with RSA-based (Rivest, Shamir and Adleman) private/public keys and digital certificates -a Diffie-Hellman key agreement protocol (MIKEY-DHSIGN) deploying digital signatures and certificates.…”
Section: Introductionmentioning
confidence: 99%
“…-The public-key encryption scheme (MIKEY-PK and MIKEY-RSA-R [33]) depends upon a public-key infrastructure that certifies the private-public keys by issuing and maintaining digital certificates. While such key management schemes provide full scalability in large networked configurations, public-key infrastructures are still not widely available, and, in general, implementations are significantly more complex.…”
Section: Introductionmentioning
confidence: 99%