Draft Agenda (v1) for the Operations & Management Open Area Meeting IETF64

["Romascanu, Dan \(Dan\)" <dromasca@avaya.com>]

Please see below for our first draft of the Operations & Management Open
Area meeting.

Please let us know if you have any comments or additional agenda items.

David Kessens & Dan Romascanu
---

Draft Agenda (v1) for the Operations & Management Open Area Meeting
IETF66

When:   TUESDAY, July 11, 2006, 1520-1720 (tentative)
Where:  Room 519A (tentative)


A. Administrative stuff
   - appointment of scribe
   - blue sheets
   - agenda bashing
   (David Kessens, Dan Romascanu)
            
            
B. Area news and updates
   (Dan Romascanu, David Kessens)
               
   10 minutes for agenda item A&B
                
                  
C. Proposed working groups

   o Recently the grow working group completed work on:
     draft-ietf-grow-anycast (BCP)
     
     Also, various proposals for doing more work related to anycast
     have been floated around. We would like to discuss what the Ops
     community feels about this topic.

   Please let us know if you would like to propose any new work in the
   Ops & Mgmt area (or relevant to the Ops & Mgmt Area) that you would
   like to discuss.

D. Security Review Guidelines

Some of our recent work encountered problems in the final phases of the 
discussions in the IESG because of security considerations sections that
were considered insufficient by the security experts. We are suggesting
that
the Security Area provide more exact criteria of what is expected in a 
security review (maybe in a document similar to RFC 4181). This item
precedes a discussion in the Security Area Directorate open meeting
later
in the week, and we would like to prepare by getting inputs from the OPS
area community. 

E. Manageability Requirements

There is no consistent approach on what kind of management information 
needs to be included in protocols developped in the IETF. Currently some
of the 
IETF Working Groups include MIB modules as part of their charters, but
not all
are being used. Other protocols (some of them non-standard) are being
used 
for management, as well as other type of data models than SMIv2 MIBs. We
would like to discuss the idea of providing guidance for operational and

manageability requirements for other areas IETF work, which would define
the management operations and data model in a more generic way.  
   
Y. Open Mike   
   
Z. AOB