Tuesday July 27 1520-1700 Session Chair: Bert Wijnen 1 Welcome and agenda bashing (scribes) chair 5 min Note takers Tom Taylor and Tina Tsou. Wes Hardaker Jabber scribe. Note Well slide displayed. Agenda accepted. 2 WG Status chair 5 min Considerable IESG and AD discussion of OAM Acronym Soup -- could be coming back to WG. 3 OAM Overview Mizrahi 10 min draft-ietf-opsawg-oam-overview Dan Romascanu relayed a comment from Jabber: The author should watch for an announcement on from the I*. IAB/IESG Workshop on Forwarding Plane OAM. October 12-14, George Mason University, Fairfax, Virginia. Bill Andersson asked what time frame for WGLC. Asked that a document being worked on in MPLS WG be considered. He also added some information relating to the Function Summary table. 4 Configuration problem statement Taylor 10 min draft-tsou-opsawg-network-configuration Thomas Narten: Concern that the proposal is to decide items that have been debated for 16 years, and really depend on the details of the deployment and infrastructure. Authors to make the scope of the draft clearer, then chairs can determine if WG willing to take on. Charter text has to be drawn up to cover the work. 5 IANA Reserved IPv4 Prefix for IPv6 Transition Weil 10 min draft-weil-opsawg-provider-address-space Q: how would it be classified? Effectively as an addition to RFC 1918 space. Point: are enterprise operators meant to use this space? Weil: really meant for service providers. 10:03:07 AM) cdl@jabber.org: The current speaker has a good point here. The authors may want to consider a recommendation that this would be focused on upstream providers. (10:03:16 AM) cdl@jabber.org: That was chair hat off, btw. Matt __: Doesn't this create another class of device that doesn't understand Chris Stanley : least objectionable solution Thomas Narten: is it a requirement from a technical viewpoint to specify management procedures for this space? Next speaker: shouldn't really be a problem because they won't have to take management actions that often. 7 Energy management framework Quittek 10 min Architecture: presented by Claise. Gives a roadmap through the drafts. Requirements: presented by Claise (continuation of previous presentation). Quick review of individual drafts in set. Dan: comment as contributor. Not convinced by the argument in the favor of pmIndex. Could discuss off-line. Wes Hardaker: pointed to context and context index to simplify. RFC 3413. Comments by Juergen Schoenwaelder, Jinwyeock 8 Energy management IDs various 20 min Considerations for Power and Energy Management draft-norwin-energy-consider Requirements for Energy Management draft-quittek-power-monitoring-requirements Power Management Architecture draft-claise-energy-monitoring-mib Power and Energy Monitoring MIB draft-claise-power-management-arch Definition of Managed Objects for Energy Management draft-quittek-power-mib 9 Power & Energy monitoring working group Claise & Quittek 10 min Presented by Juergen Quittek. Some concern with wording of part 2 of work item description. Reword charter items: "publish" -> "Accept Working Group draft". Thomas Narten asked: why make it a Working Group? Answer: to give identifiable point of contact for other SDOs. Margaret Wasserman: who will use this? Wes: has three customers crying for MIBs. ___: This work overlap with all sorts of work the IETF is doing. Thomas Narten: understands that there is a demand. But will the DMTF and IETF work in harmony on this topic. Dan Romascanu: If this went to a WG, would have to verify with external bodies that this is not in conflict with or a duplication of their work. Dan: further remarks. Can see the energy. Not yet decided how to proceed. Do we need to continue these discussions in OPSAWG or in a new WG? Hum: stronger for starting a new WG. Dan inclined to create non-WG discussion list to continue the charter discussion.