Dean Willis | 8 Mar 2007 01:05
Favicon

Registration of MIME media type application/pkcs8 (possible resubmit)


It's possible that this has been previously brought to this list --  
if so, please slap me around appropriately and point me at the  
review. I was unable to locate it in the mailing list archives.

I'm working through a PROTO writeup on:

http://www.ietf.org/internet-drafts/draft-ietf-sip-certs-03.txt

which contains the following MIME type registration.

---------

    Subject: Registration of MIME media type application/pkcs8

    MIME media type name: application

    MIME subtype name: pkcs8

    Required parameters: None

    Optional parameters: None

    Encoding considerations: The PKCS#8 object inside this MIME type
                             MUST be DER-encoded.

                             This MIME type was designed for use with
                             protocols which can carry binary-encoded
                             data. Protocols which do not carry binary
                             data (which have line length or
(Continue reading)

Bjoern Hoehrmann | 12 Mar 2007 15:51
Picon

Re: Registration of MIME media type application/pkcs8 (possible resubmit)

* Dean Willis wrote:
>I'm working through a PROTO writeup on:
>
>http://www.ietf.org/internet-drafts/draft-ietf-sip-certs-03.txt
>
>which contains the following MIME type registration.

>    Encoding considerations: The PKCS#8 object inside this MIME type
>                             MUST be DER-encoded.
>
>                             This MIME type was designed for use with
>                             protocols which can carry binary-encoded
>                             data. Protocols which do not carry binary
>                             data (which have line length or
>                             character-set restrictions for example)
>                             MUST use a reversible transfer encoding
>                             (such as base64) to carry this MIME type.
>                             Protocols that carry binary data SHOULD
>                             use a transfer encoding of "binary".

As I read RFC 4288, this should say 7bit, 8bit, binary, or framed, not
you have there now.

>    Security considerations: Carries a cryptographic private key

Is that all that can be said here? For example, doesn't the format
specification have security considerations that could be referenced?

>    Interoperability considerations: None
>
(Continue reading)

Magnus Westerlund | 29 Mar 2007 11:56
Picon
Favicon

Re: Request for review update of media types audio/3gpp and video/3gpp

Hi,

There has been some minor updates to the media type definition. The 
security consideration section has been updated and some other smaller 
wording changes. We now believe this to be ready to replace RFC 3839. 
Unless there are comments on this before 13th of April we will request 
that IESG approve this registration update.

Full text in Word:
http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/Specs_update_after_SA35/26244-710.zip

Only media type template in PDF:
www.denstore.se/IETF/media-types-26244-710.pdf

Cheers

Magnus

Magnus Westerlund skrev:
> Hi,
> 
> The two media types audio/3gpp and video/3gpp was defined in RFC 3839:
> ftp://ftp.rfc-editor.org/in-notes/rfc3839.txt
> 
> With the publication of the codecs parameters in RFC 4281
> (ftp://ftp.rfc-editor.org/in-notes/rfc4281.txt) these two media types 
> should be updated to include this parameter. This 3GPP defined file 
> format has also got a few more features, one include the capability of 
> embedding other binary objects to be used in scene presentations created 
> by SMIL or SVG to achieve self contained units. Due to this the RFC 
(Continue reading)

Magnus Westerlund | 29 Mar 2007 11:56
Picon
Favicon

Re: Request to review Media Type */rtp-enc-aescm128 for 3GPP

The correction to this media type has been introduced. The result is 
available here:

Only media types in PDF:
www.denstore.se/IETF/media-types-26234-720.pdf

Full word version:
http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/Specs_update_after_SA35/26234-720.zip

Unless there are any further comments before the 13th of April we plan 
to request that IESG approve the registration of this media type.

cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund <at> ericsson.com
----------------------------------------------------------------------

Magnus Westerlund | 29 Mar 2007 13:11
Picon
Favicon

Re: Request for review of 9 MIME type for 3GPP SA4

Hi,

There was no comments on the latest request. However as I know actually 
intend to take care of these media type registrations I like to ensure 
that no one has any further comment on the current version of the 3GPP 
specification of the media types. The latest version of the 
specification is:

Whole document in Word format:
http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/Specs_update_after_SA35/26346-730.zip

Media types only in PDF:
www.denstore.se/IETF/media-types-26346-730.pdf

Please provide any comments by 13th of April.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund <at> ericsson.com
----------------------------------------------------------------------

(Continue reading)


Gmane