1 / 8

Visual Networks MIB Update: Latest Changes and Compliance Evolution

This draft provides an overview of the latest updates to the Visual Networks MIB and details the compliance evolution process. It includes revisions, editorial modifications, and completeness checks, aiming for a seamless transition to the RFC Editor stage.

rene
Download Presentation

Visual Networks MIB Update: Latest Changes and Compliance Evolution

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. draft-ieft-frnetmib-frs-mib-10.txt Ken Rehbehn Visual Networks IETF 47 - Adelaide

  2. Status • WG last call completed 11/30 • IESG last call issued 12/8 • Erik Nordmark's comments 12/30 • (s/MUST/must/, s/SHOULD/should/) • MIB Doctor’s comments 1/5 • New draft addressing the MIB Doc's concerns 3/8 • Two additional issues before going to RFC Editor • compliances • max fragment size

  3. Minor Changes since -09 • Numerous editorial modifications • completeness of REFERENCES, size ranges • move comments into DESCRIPTION clauses • Concentrated list of changes since RFC 1604 into single complete list

  4. More significant … • Removed "stack" picture • Killed frLportVCSigPointerAdmin • Changed the notification OBJECT IDENTFIER to avoid conflict with obsolete trap • Re-organized the compliance groups

  5. Compliance EvolutionRFC 1604 frnetservConformance frnetservGroups (1) frnetservLportGroup (1) frnetservMgtVCSigGroup (2) frnetservPVCEndptGroup (3) frnetservPVCConnectGroup (4) frnetservAccountPVCGroup (5) frnetservAccountLportGroup (6) frnetservCompliances (2) frnetservCompliance (1)

  6. Compliance EvolutionDraft -09 -09 RFC 1604 frnetservConformance frnetservGroups (1) frnetservLportGroup (1) frnetservMgtVCSigGroup (2) frnetservPVCEndptGroup (3) frnetservPVCConnectGroup (4) frnetservAccountPVCGroup (5) frnetservAccountLportGroup (6) frnetservPVCNotifGroup (7) **** NEW/DEP frnetservPVCNotifGroup2 (8) frnetservCompliances (2) frnetservCompliance (1) **** DEP frnetservCompliance2 (2) **** NEW frnetSwitchGroups (3) **** NEW frnetSwitchLportGroup (1) **** NEW frnetSwitchMgtVCSigGroup (2) **** NEW frnetSwitchCompliances (4) **** NEW frnetSwitchCompliance (1) **** NEW frnetservConformance frnetservGroups (1) frnetservLportGroup (1) frnetservMgtVCSigGroup (2) frnetservPVCEndptGroup (3) frnetservPVCConnectGroup (4) frnetservAccountPVCGroup (5) frnetservAccountLportGroup (6) frnetservCompliances (2) frnetservCompliance (1)

  7. Compliance EvolutionDraft -10 -10 RFC 1604 frnetservConformance frnetservGroups (1) frnetservLportGroup (1) frnetservMgtVCSigGroup (2) frnetservPVCEndptGroup (3) frnetservPVCConnectGroup (4) frnetservAccountPVCGroup (5) frnetservAccountLportGroup (6) frnetservLportGroup2 (7) **** NEW frnetservPVCEndptGroup2 (8) **** NEW frnetservPVCConnectNamesGroup (9) **** NEW frnetservLportAdminGroup (10) **** NEW frnetservMgtVCSigAdminGroup (11) **** NEW frnetservPVCNotifGroup (12) **** NEW/DEP frnetservPVCNotifGroup2 (13) **** NEW frnetservCompliances (2) frnetservCompliance (1) **** DEP frnetservCompliance2 (2) **** NEW frnetSwitchCompliance (3) **** NEW frnetservConformance frnetservGroups (1) frnetservLportGroup (1) frnetservMgtVCSigGroup (2) frnetservPVCEndptGroup (3) frnetservPVCConnectGroup (4) frnetservAccountPVCGroup (5) frnetservAccountLportGroup (6) frnetservCompliances (2) frnetservCompliance (1)

  8. One last issue • frLportFragSize Integer32 (0..8184) • Change to 4096

More Related