Coordinates

• H.323: NIFF/HUNGARNET MCU GDS: 0036100309901
• Phone: +36 1 666 1111 (type GDS number 0036100309901) https://wiki.voip.niif.hu/index.php/En-faq-pstndialin

Attending

• Jason Zurawski (Internet2)
• Roman Lapacz (PSNC)
• Sławomir Trzaszczka (PSNC)
• Piotr Pikusa (PSNC)
• Aaron Brown (Internet2)
• Jeff Boote (Internet2)
• Cándido Rodríguez (RedIRIS)
• Freek Dijkstra (SARA)
• Nina Jeliazkova (BREN)
• Michael Bischoff (SurfNET)

Apologies

• Martin

Agenda

• Review actions from last meeting
  • COMPLETE - All: Review documents if you haven't done so
  • NOT COMPLETE - All: Review NMC-Base_TODO and NMC-MA_TODO, see if you have an assignment.
  • COMPLETE - Roman: Find contact information for GN3 contributor looking at netconf vs perfSONAR protocols
  • COMPLETE - Jason: Set agenda for next time, update notes.
  • NOT COMPLETE -Freek: Review and correct RFC 2119 words.
• Review recent comments on documents
• Direction and attempting to lock down the protocol(s) (Jeff/Jason)
• OGF 28 News
• Next Meeting

Notes

Review recent comments on documents

From mail:

• Use the RFC 2119 words correctly and uniformly - This has already been assigned to Freek but Inder should help as well
• Full specification of protocol exchanges (full request/response examples - eliminate ambiguity). Clarifications regarding 'optional' elements and the responses that are elicited
• Explain the statefullness of the 'id' and 'idRef' elements
• Chaining confusion - see below.

Notes:

JZ: Thanks all for the comments, but we also need to start working on the doc. If you have structural comments, fix them. If you have content comments, we can talk on the mailing list. RL: Don't want Chaos. JZ: True, but we are using SVN. Make a comment (use the '%' character) in the tex source if you are unsure. language choice/spelling can always be fixed (and reversed)

JZ: Will be spending more time on this between Feb 8th and March 5th in preparation for OGF28.

RL: Need to resolve the XSD v RNC debate JZ: I didn't see anyone else with opinions, would rather stay with RNC FD: Mentions that other groups do use it, but doesn't think this is a problem JB/JZ/RL: Doesnt seem to be any clear reason to switch (no benefits), RNC is readable and we can easily translate to XSD later

Gn3 project to use netconf instead of pS protocols

Roman will have more information on the documentation and a demonstration very soon. Coordinating with Gn3 team, and there is some need to finish things before they are made public.

RFC 2119 Words

Freek has made notes on paper, will start to commit to SVN soon. Inder from ESnet will be helping.

Direction and attempting to lock down the protocol(s)

Jeff has proposed on the mailing list (and the last meeting) that we should consider this document to not be an exact snapshot of what is used in in current resources, but something that tries to correct the blemishes of the past while still being true to what works today. This would essentially mean:

• Altering the base document to remove protocol ambiguity
  • The example given in email was the differences between using an attribute vs an element in certain situations
  • Other examples include setting a specific time format, permitting a small subset of parameter combinations, and (severely) limiting chaining combinations
• Using a specific (non-'nmwg') namespace, perhaps using something that references NMC and following GFD 84
• Strictly specifying the action/re-action on protocol exchanges. This would entail very specific schematic rules and would rely on other in progress work like result codes

Notes:

JZ/JB introduce the idea. Really want to have a stable, predictable, well specified protocol. There will be things to consider external to NMC:

• What will pS need to do, short and long term
• Who from pS needs to be involved
• Backwards compat

FD: interested to know what this will do to running software. JB to RL: most concerned about what this would mean to something like E2Emon. RL agrees that this may be something to involve pS people on, at least as an FYI (may not help design things, but will have opinions on transition, etc.). JB and RL talk about DICE meeting (March), may get discussed there if there are people who are interested.

RL: Action to identify who in Gn3 should be notified/involved JZ: Action to mail the RL people + pSPS people as a starting point.

OGF 28 News

Registration and Lodging info posted here . Agenda is not set yet, in the past the networking groups (NMC, NM, NML, NSI) were all treated as mutually exclusive entities and were positioned close together. Jason is trying to get a copy of the draft schedule but has been unsuccessful so far.

Action: JZ will continue to search for an agenda. <inder> based on what I have seen, NMC and NML are scheduled currently for Tuesday, NSI for Wed/Thurs, new BOFs on Monday

Other Topics

• Nothing decided for result codes yet, JZ will kick the mailing list to get more comments.

Next Meeting

Feb 11th, 2010 - 16:00 UTC

Actions

* All: Review NMC-Base_TODO and NMC-MA_TODO, see if you have an assignment, and start working. * Freek & Inder: Review and correct RFC 2119 words. * Roman: Identify who in Gn3 should be notified/involved regarding our attempts to lock down the protocol * Jason: Mail the people from Gn3 and pSPS regarding the locking down of the protocol * Jason: Keep up the hunt for the OGF 28 agenda * Jason: Spur the result code discussion on Result Codes