Skip to main content

A set-key attribute for symmetric-key packages
draft-herzog-setkey-07

Discuss


Yes

(Tim Polk)

No Objection

(Stewart Bryant)

No Record

Deb Cooley
Erik Kline
Francesca Palombini
Gunter Van de Velde
Jim Guichard
John Scudder
Mahesh Jethanandani
Murray Kucherawy
Orie Steele
Paul Wouters
Roman Danyliw
Warren Kumari
Zaheduzzaman Sarker
Éric Vyncke

Summary: Needs a YES.

Deb Cooley
No Record
Erik Kline
No Record
Francesca Palombini
No Record
Gunter Van de Velde
No Record
Jim Guichard
No Record
John Scudder
No Record
Mahesh Jethanandani
No Record
Murray Kucherawy
No Record
Orie Steele
No Record
Paul Wouters
No Record
Roman Danyliw
No Record
Warren Kumari
No Record
Zaheduzzaman Sarker
No Record
Éric Vyncke
No Record
Alexey Melnikov Former IESG member
Discuss
Discuss [Treat as non-blocking comment] (2011-03-07) Unknown
I have small issue I would like to discuss before recommending approval of this document:


2.  The set-key attribute

   As above, this structure may be expanded at a later date with
   additional types.  Implementations SHOULD gracefully handle values
   and types which they do not recognize.

How can the SHOULD be satisfied in an interoperable way? By ignoring them?

How is extensibility going to work in a general case? Handling of a union versa handling of an intersection are going to produce quite different results.

Tim Polk Former IESG member
Yes
Yes () Unknown

                            
Stewart Bryant Former IESG member
No Objection
No Objection () Unknown