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

Discuss

(Alexey Melnikov)

Yes

(Tim Polk)

No Objection

(Stewart Bryant)

No Record

Alvaro Retana
Andrew Alston
Erik Kline
Francesca Palombini
John Scudder
Lars Eggert
Martin Duke
Murray Kucherawy
Paul Wouters
Robert Wilton
Roman Danyliw
Warren Kumari
Zaheduzzaman Sarker
Éric Vyncke

Summary: Needs a YES.

Alvaro Retana No Record

Andrew Alston No Record

Erik Kline No Record

Francesca Palombini No Record

John Scudder No Record

Lars Eggert No Record

Martin Duke No Record

Murray Kucherawy No Record

Paul Wouters No Record

Robert Wilton No Record

Roman Danyliw No Record

Warren Kumari No Record

Zaheduzzaman Sarker No Record

Éric Vyncke No Record

(Alexey Melnikov; former steering group member) Discuss

Discuss [Treat as non-blocking comment] (2011-03-07) 
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 steering group member) Yes

Yes () 

                            

                        
                    

                
            
        
            
                
                    

                        (Stewart Bryant; former steering group member)
                        
                            
                            No Objection
                            
                        
                    

                    

                        

                            

                                No Objection 
                                
                                    ()