1 / 4

Adrian Farrel (adrian@olddog.co.uk)

This draft outlines the mandatory Manageability Section guidelines for all PCE Working Group I-Ds to ensure proper control and monitoring processes are established. It provides specific requirements and advice on section content.

ianlewis
Download Presentation

Adrian Farrel (adrian@olddog.co.uk)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Requirements for Manageability Sections in PCE Working Group Draftsdraft-farrel-pce-manageability-requirements-01.txt Adrian Farrel (adrian@olddog.co.uk) 67th IETF, San Diego, November 2006

  2. History • Originally floated as a proposal for the whole Routing Area • Too ambitious • Need to prove the cost/benefit • Discussed at PCE in Dallas (IETF-65) • Working group I-D editors seemed amenable • Working group seemed to support the idea • Chairs enthusiastic • RFC 3933 experiment proposed at Ops Area meeting in Montreal • Opinion was that an experiment was too heavy • This draft in October 2006 • Rev 01 with typo fixes almost at once 67th IETF, San Diego, November 2006

  3. What Will be Required? • Like mandatory Security Considerations • Manageability Section • MUST be present in all PCE WG I-Ds • MAY be “empty”, but MUST explain why • If present then MUST contain specific subsections • Control of Function and Policy • Information and Data Models, e.g. MIB module • Liveness Detection and Monitoring • Verifying Correct Operation • Requirements on Other Protocols and Functional Components • Impact on Network Operation • Advice on content of sections is given 67th IETF, San Diego, November 2006

  4. Next Steps • Incorporate feedback already received from Ops Area AD • New revision November • Become PCE WG I-D • December • Thorough review from working group • You will have to implement it, so you MUST review it • December • WG last call January 2007 • Desire conformance now • Require conformance after WG last call 67th IETF, San Diego, November 2006

More Related