Liaison statement
OMA-LS 0109 Liaison Statement to IETF Request IANA Registration of a new MIKEY General Extension Payload
Additional information about IETF liaison relationships is available on the
IETF webpage
and the
Internet Architecture Board liaison webpage.
State | Posted |
---|---|
Submitted Date | 2006-05-23 |
From Group | OMA |
From Contact | Dean Willis |
To Group | IESG |
To Contacts | iesg@ietf.org |
Cc | mark.cataldo@openwave.com ileana.leuca@cingular.com dean.willis@softarmor.com |
Response Contact | Lakshminath Dondeti <ldondeti@qualcomm.com> |
Technical Contact | Lakshminath Dondeti <ldondeti@qualcomm.com> |
Purpose | For action |
Deadline | 2006-06-12 Action Taken |
Attachments | Original PDF of OMA LS 109 |
Body |
1 Overview The Open Mobile Alliance's (OMA) Browser and Content (BAC) Broadcast (BCAST) group's Service and Content Protection specification defines the use of a short term key message (STKM) and a long term key message (LTKM) that carry attributes related to service and content protection. An IETF draft, draft-dondeti-msec-mikey-genext-oma, specifies the use of the General Extension payload of MIKEY (RFC 3830) to carry the LTKMs or STKMs. For that purpose, OMA BCAST requests IANA registration of a new MIKEY General Extension Payload. 2 Requested Action(s) BCAST kindly asks expedited processing of draft-dondeti-msec-mikey-genext-oma and requests registration of a new MIKEY General Extension Payload for use by OMA BCAST specifications. The contents of the payload itself are defined in the OMA Service and Content protection specification and are not provided in the IETF draft. The IETF draft along with the OMA Service and Content protection specification have sufficient detail for interoperable implementations. 3 Conclusion We thank you for your consideration. With best regards, OMA BAC BCAST (Mobile Broadcast Services sub working group) |