100 likes | 191 Views
OPS Area Open Meeting w w w.ops.ietf.org mailing list: ops-area @ ops.ietf.org David Kessens (david.kessens@nokia.com) Bert Wijnen (bwijnen@lucent.com) slides: kessens.com/~david/presentations/OpsArea61.ppt. OPS AREA Agenda 1/2. Administrivia News from working groups Opsec (5 min)(David)
E N D
OPS Area Open Meetingwww.ops.ietf.orgmailing list: ops-area @ ops.ietf.orgDavid Kessens (david.kessens@nokia.com)Bert Wijnen (bwijnen@lucent.com)slides:kessens.com/~david/presentations/OpsArea61.ppt
OPS AREA Agenda 1/2 • Administrivia • News from working groups • Opsec (5 min)(David) • AAA & Diameter Maintenance(5 min)(Bert) • CAPWAP (5 min) (Bert) • BRIDGEMIB, move to IEEE802.1 (5 min) (Dave/Dan) • Collaboration with other organizations w.r.t. Network Management (10 min)Bert • NGN Network Management • Collaboration w.r.t. WebServices Based NM (GGF, DMTF, OASIS, W3C, IETF) • Management Considerations section? • The future of NETCONF once the protocol & mapping documents are done • Simon Leinen (10 min), discussion (15 min)
OPS AREA Agenda 2/2 • OPS area work of cross-area interest • Status of multi6 (15min) (Erik N) • Future of v6ops (15min) (David) • Overview MBONED work on: MP-LSPs and p2mp te lsps (5 min) Dave Meyer • OPS protocol work (5min)(David) • discussion (15min) • Open mike
AAA & Diameter Maintenance • AAA WG is nearly done • But needs to actually FINISH all work first • aaa-eap is on IESG plate • aaa-sip-application and aaa-uri ? • New Diameter Maintenance WG (DIAM) ? • focus on maintenance • Possibly advancing Diameter to DS • BCP on inter-working AAA & Radius • Place to discuss new requirements from other WGs or Organizations and decide if work needs to be done • Modeled after TCPM (TCP Maintenance)
CAPWAP – re-chartered • Initial (architecture taxonomy) work completed, reasonably on time, even on aggressive schedule • New work is to develop a stds track CAPWAP protocol • CAP == Control and Provisioning • Not other non-mgmt WAP issues • Aggressive DEADline for objectives • Close co-ordination with IEEE 802.11
Collaboration for NGN NM 1/2 • ITU-T has a FG (Focus Group) on NGN • Other orgs (ETSI, OASIS,…) providing input to ITU-T FG • ITU-SG4 now gets input from a new FG on NGN management • We had informal (phone) discussions between people from ITU, ETSI, TMF, IETF,… on possibly working together • Open for (individual) participation: • Mailing list being setup • FTP site being setup for doc sharing • Participation on individual basis • We had first call (Nov 1st) with some IETFers present. • We can individually or as WGs send input
Collaboration for NGN NM 2/2 • See recent postings to ops-area list: • archive: http://ops.ietf.org/lists/ops-nm/ops-nm.2004 • 1st msg: http://ops.ietf.org/lists/ops-nm/ops-nm.2004/msg00005.html
Collaboration for DataModeling • Collaboration w.r.t. WebServices Based NM (GGF, DMTF, OASIS, W3C, IETF) • Had informal discussions between “leadership” (so Bert participated) • Information exchange • Try to avoid duplicate work • MoU being specified (?? Mmm ??) • Impact on our (Netconf) Datamodel?
Collaboration for DataModeling • Coordination & Communications • Ongoing template to track issues/actions in the “landscape” of our work • Governance • Executive, Technical, liasison-person • Pre-planned calls and f2f meetings • Goal is to encourage information sharing • Initial Efforts/Task: • Landscape doc • Definitions and Taxonomy doc • White paper, FAQ, Powerpoint presentations (!?)
Management Considerations Section • RTG area has a (individual) proposal to require this • See: draft-farrel-rtg-manageability-requirements-00.txt • Pls read/comment • Opinions?