Access Node ANCP MIB

1
Access Node ANCP MIB

• ANCP WG
• IETF 70 Vancouver
• draft-ietf-ancp-mib-an-01.txt
• Stefaan De Cnodder
• Moti Morgenstern

2
History

• March 2007 IETF 68 Prague
• draft-decnodder-ancp-mib-an-01.txt presented
• On mailing discussed and accepted as WG draft
• June 2007
• draft-ietf-ancp-mib-an-00.txt submitted
• November 2006 IETF 70 Vancouver
• draft-ietf-ancp-mib-an-01.txt submitted

3
Partitioning (v00-v01)

• Added a scalar ancpAnPartitionsUsed to configure
  whether partitions are used or not.
• if partitions used, the configured partition ID
  for the sessions must be non-zero, and is ignored
  otherwise
• ancpAnInterfaceConfigTable rows should only be
  created automatically when partitions are used
  default partition ID is 0, meaning that the line
  is not yet assigned to any partition
• Changed from v00 -gt v01
• this scalar is changed into to SYNTAX
  TruthValue
• description of ancpAnSessionConfigPartitionId
  modified accordingly

4
Notifications (v00)

• Attributes have been added such that the UP and
  DOWN notifications can be enabled/disabled per
  session
• ancpAnSessionConfigNotifyDnEnable
• ancpAnSessionConfigNotifyUpEnable
• Changed from v00 -gt v01
• These two objects have been made read-create
  rather than read-write

5
Modifying Attributes (v00)

• When a session is configured, its attributes can
  only be modified when rowStatus is set to
  notInService
• an implementation may tear down and set up the
  session again

6
Other smaller changes in v00

• Editorial updates
• ancpAnSessionConfigGsmpRetryTimer changed to
  ancpAnSessionConfigAncpRetryTimer
• ancpNotifications changed to ancpAnNotifications

7
Session Index (v01)

• ancpAnSessionConfigSessionID
• (Index of ancpAnSessionConfigTable)
• The session ID is not a system generated index
• Extra clarification in DESCRIPTION session ID
  must be unique across all partitions

8
IP addresses (v01)

• All objects with an IP address have a
  corresponding object indicating the type of the
  IP address
• v01 improves the DESCRIPTIONS by explicitly
  referring to the corresponding object indicating
  the type

9
Port Number (v01)

• ancpAnSessionConfigEncapPortNumber
• port number of the Transport Protocol
• the MIB is not limited to TCP
• zero is excluded from the values range
• more details in DESCRIPTION provided, in
  particular
• port number must be 6068 in case of TCP
• other values are only relevant in case of no TCP

10
Next Steps

• Some considerations
• MIB depends on protocol specification, e.g.,
  changing capabilities might impact MIB as well
• Align document structure withdraft-harrington-tex
  t-mib-doc-template-03.txt