Coordinates

• GDS Dialing Directions:
  • Register with a GDS-enabled Gatekeeper. To borrow space see: https://wiki.internet2.edu/confluence/display/I2commons/H.323+Testing+Instructions
  • Make sure you are connecting at your maximum available speed, up to 1536Kbs
  • Dial 001189 780 0199999 (no spaces)
• IP Dialing Directions:
  • Dial 192.148.244.154.
  • Press # key to bring up keypad
  • Enter 0199999# to enter the conference

Attending

• Jason
• Aaron
• Freek
• Roman
• Jeff

Excused

• N/A

Agenda

• Result codes final thoughts
• Getting the NMC Base document done (and into the std track)
• Next steps

Notes (courtesy of Jason)

Jason circulated minor changes to document. Minor discussion on this, no show stoppers. Jason volunteers to add into real document (now that svn is working again...). Deadline - 2 weeks.

Want to put this to bed int he OGF ASAP. Requested GFD numbers from Richard, did not hear back. Will pester again. Once we have the number, put doc into the system. 90 day turn around (if we are lucky). Need two pre-editors. Scott Brim (Internet2) and Gina Kramer (Dante) suggested.

Jeff/Roman talk a bit about if Josva Kliest (sp?) has been involved. He is doing 'production' for the most part. Roman will send him an email, let him know what we are doing and if there is other help available.

Roman poses another question - when could pSPS (and MDM) get the result codes we worked on implemented. Lots of talk - bottom line is that Jeff/Aaron need justification for projects and need to work in terms of operational needs. Can't re-invent if something isn't _broken_. Unlikely to implement the new result codes in old services unless there is clear benefit for clients. (New functionality or fixing a problem.) New services could use the approach.

Bleeds into longer discussion about why we are doing standards. Our approach was a bit backwards, we had products and now we want to standardize to encourage adoption in other areas. Idea is put forward to 'document as things are developed' - e.g. something like a new API - and OGF could publish as an informational. Jeff/Aaron may float this internally (and in DICE). Jason could help with publication aspects in OGF, since he is not doing operational aspects.

Notes (courtesy of Freek)

The group of Aaron and Jeff moved to operations. This means that there should be a result of any activity in 6-12 months time, as opposed to 2-3 years. Lately, the focus of DICE has been on deployment, not on further improvements.

Cloud providers

OGF moves too slow, even though it moves faster than the IETF. Commercial providers prefer to just publish a white paper listing their API, since they know it will change next year anyway. Also, since this is relative new, having a better API is still a competitive advantage.

Documentation of service

Not all DICE services are documented. Instead of ask for the best API, just document the current API as informational. Suggestion to move document forward, ask community if it is good or bad (yeah or nay). That would reduce the amount of effort required, even if the result is perhaps not as perfect. Jeff and Aaron like to involve developers to formulate their API, and can help writing down the results. Jason could push the 'boilerplate' aspect through the office of the CTO.

Actions

• Martin/Ezra to share the data from ESCPS/Periscope (old action)
• Jason will merge result codes into real document. Do edit pass.
• Jason will find a reader at Internet2 (Scott Brim has volunteered)
• Roman will find a reader at Geant (Gina Kramer, Dante)
• Roman to email Josva (CC Jeff) about participation in this process
• Jason will bother RHJ about GFD numbers, again

Next Meeting

• Jan 19th, 16:00 UTC

Attachments:

20120105-NMCResultCodes.docx [20120105Notes/20120105-NMCResultCodes.docx]