60 likes | 218 Views
SACM IETF 89, London, UK. Dan Romascanu Adam Montville . Note Well. This summary is only meant to point you in the right direction, and doesn't have all the nuances. The IETF's IPR Policy is set forth in BCP 79; please read it carefully. The brief summary:
E N D
SACMIETF 89, London, UK Dan Romascanu Adam Montville
Note Well This summary is only meant to point you in the right direction, and doesn't have all the nuances. The IETF's IPR Policy is set forth in BCP 79; please read it carefully. The brief summary: • By participating with the IETF, you agree to follow IETF processes. • If you are aware that a contribution of yours (something you write, say, or discuss in any IETF context) is covered by patents or patent applications, you need to disclose that fact. • You understand that meetings might be recorded, broadcast, and publicly archived. For further information, talk to a chair, ask an Area Director, or review the following: BCP 9 (on the Internet Standards Process) BCP 25 (on the Working Group processes) BCP 78 (on the IETF Trust) BCP 79 (on Intellectual Property Rights in the IETF)
Administrative Tasks • Blue sheets • Two note takers • Jabber scribe
Agenda • 1. Note Well, Note Takers, Jabber Scribes, Agenda Bashing - Chairs (5 min) • 2. Charter and Milestone Review - Chairs (10 min) • 3. Terminology - Adam (15 min) • 4. Use Cases - David (45 min) • 5. Requirements - Nancy Cam-Winget (45 min) • 6. Telecom Requirement - Minpeng (10 min) • 7. Next Steps - Architecture and Information Model (20 min) • 8. Open Microphone, Way Forward - available time
WG Status • We are not doing great on milestones • Oct 2013 Initial submission of SACM Architecture Internet-Draft • Nov 2013 Initial submission of SACM Information Model Internet-Draft • Jan 2014 Initial submission of protocol and data format for retrieving configuration and policy information for driving data collection and analysis Internet-Draft • Jan 2014 Initial submission of protocol and data format for collecting endpoint posture Internet-Draft • But maybe there is a good reason • Focused on use cases, terminology, requirements – split from architecture • https://datatracker.ietf.org/doc/draft-ietf-sacm-terminology/ • https://datatracker.ietf.org/doc/draft-ietf-sacm-use-cases/ • https://datatracker.ietf.org/doc/draft-camwinget-sacm-requirements/ • Virtual Interims – seem to be useful
Way Forward • New Milestones in the charter • 2014-03-31 – Requirements Update Submitted • 2014-03-31 – Terminology and Use Case update and WGLC • 2014-04-15 – Adopt Requirements I-D • 2014-04-15 – Initial Architecture submissions • 2014-05-15 – Adopt Architecture I-D • 2014-06-15 – Initial Submission of Information Model • One or two Virtual Interims • IETF 90 • Close outstanding architectural issues • Field objections to Information Model submission