PMC Minutes for 2009-06-24
Attendees
Rob
John
Rainey Fellows - iMatix
Pranta Das - Cisco
Colin MacNaughton - Progress
Hanno Klein - DBS
Andreas Moravec - DBS
Rafi Schloming - RedHat
Roshan D'Mello - Credit Suisse
Mark Blair - Credit Suisse
Alexis Richardson - RabbitMQ
Matthew Arrott - TWIST
Apologies
Carl Trieloff
Paul Freemantle
David Ingham
Robert Grieg
Agenda
1-0 Update
1-0 vs 1-1 Scope
User SIG
Budget
AOB
1-0 Update
Updates have occurred on the data types and format
More generic way of representing application level types
Mark would like presentation on Security
Other updates
Matthew continues work on mapping AMQP and John Day networking models
More people interested in joining Message Format discussions
Offer to bring existing message format technology to AMQP
1.0 prioritisation
- Features in 1.0 or pushed back to 1.1
- Message Format
- Properties
- Base content
- Security
- Client/Broker authentication
- Message Authentication (signing etc)
- DTX
- others?
Agreement that on security:
in scope - client to broker authentication, SSL
out of scope - message signatures, end-to-end authentication
Rafi: issue with kerberos and re-keying
no way to re-key once ticket expires
JOH: suggest we don't standardize on Kerberos for 1-0, but later
MA: We have guys looking at this
Are we standardizing on this? We should be careful on this
X.509 works better across organisational boundaries
RG: it's not an AMQP or Kerberos problem... it's a SASL problem
RS: it's an issue with the way SASL integrates with protocols with security layers with rekeying
JOH: need to create a certainty what we are doing for 1-0... If there is a workaround in SASL then we should use that.
MA: For 1-0 we use SASL and then the community can decide if we need to solve the Kerberos problem for 1-1
JOH: for 1-0 we need a type system is needed for selectors, but not necessarily a whole message format.
RS: There are going to be multiple message formats.
MA: Agree with RS
RS: You need a format-id and the bytes
JOH: Need format for properties.
JOH: Would need a format for management
RS: would be good to have something that can represent a "Map Message"
RG: management in 1-1?
JOH: Agree management should be in 1-1
Security
peer to peer Authentication and encryption in
end to end MACs 1-1
DTX 1-1
Management 1-1
Failover Exchange 1-1
Message Format 1-1
Properties 1-0
Global Addressing - MA would like to set up a call
RS: should amqp$transfer be in 1-0
RG / JOH : We should have a position paper
MA: Free from week beginning 7th
Set up meeting with MA/JOH/RG/RS pre-meeting to discuss architectural model
Then want to have meeting on the modelling of the protocol on PMC
Funding
John still working on funding proposal - report back next month