NSIS resilience draftvandenboschnsisresilience00'txt

1
NSIS resiliencedraft-vandenbosch-nsis-resilience-
00.txt

• sven.van_den_bosch_at_alcatel.be
• maarten.buchli_at_alcatel.be

2
Scope

• Interim meeting discussion
• Error-handling
• Asynchronous events from network
• Sender/receiver initiated reservations
• Bi-directional path setup/failure
• Failure and recovery scenarios
• Consideration of different reliability for
  different network types
• Fail-over to other system
• Error notification and location relation to
  security
• Request for individual submissions
• Relation to other drafts
• draft-ietf-nsis-req-03.txt
• Open issues on error handling
• draft-hancock-nsis-fw-00.txt
• Difference in/out band
• Upper/Lower Layer failure handling

3
Discussion in draft

• Failure detection notification
• Non-NSIS host
• Synchronization between duplicate NEs
• Potential issues for
• Per-class state
• Bi-directional reservations
• Recovery
• Force route change to initiate reservation
• Duplicate reservation in upstream domains
• Delayed recovery ACKs
• Reversion
• Discovery protocol should be standardized
• Delay until reservation is complete
• Should be disabled in case of NE duplication for
  backup

4
Comments

• Terminology will be updated in -01
• Per-class state discussed on the list
• Notification
• Recovery issues
• Limited number of examples propose to add
  explicit text covering
• Sender/receiver initiation
• Bi-directionality
• Upper/lower-layer failure
• Additional failure detection mechanisms
  reference RMD
• Clarification
• internal data plane failures should not involve
  NSIS signaling
• hierarchical failures (link with severe
  congestion)
• inter-domain failures duplicate reservation
• reversion

5
Next steps

• Is this a good start for an NSIS resilience
  draft?
• If yes,
• make proposed updates and issue 01
• might consider this to be a work item for WG