Skip to main content

Syntax for Binding Documents with Time-Stamps
RFC 5544

Yes

(Tim Polk)

No Objection

Lars Eggert
(Cullen Jennings)
(Jari Arkko)
(Magnus Westerlund)
(Russ Housley)

No Record


Note: This ballot was opened for revision 06 and is now closed.

Lars Eggert (was Discuss) No Objection

(Tim Polk; former steering group member) Yes

Yes ()

                            

(Chris Newman; former steering group member) No Objection

No Objection (2008-10-08)
One observation that might be an issue if this went through IETF review:

The "PrintableString" ASN.1 type doesn't permit all the characters that are permitted in a MIME media type.  Of the US-ASCII set, only space, ctrls, and MIME tspecials are disallowed in a MIME media type.  We have registered media types that use "_", which I don't think is permitted in PrintableString.  You might want the ASN.1 type for mimeType to be IA5String.  Also, what about media type parameters?

(Cullen Jennings; former steering group member) No Objection

No Objection ()

                            

(Jari Arkko; former steering group member) No Objection

No Objection ()

                            

(Magnus Westerlund; former steering group member) No Objection

No Objection ()

                            

(Russ Housley; former steering group member) No Objection

No Objection ()

                            

(Lisa Dusseault; former steering group member) No Record

No Record (2008-10-09)
Does this commit the IETF to some kind of maintenance for this non-IETF document?

        Additional types of evidence may be used after having registered them 
        (and having had a distinguishing tag assigned to them) with the IETF. 
        A suitable registration procedure should be defined for that purpose. 

Additionally, I don't know if IANA's concern is resolved.