Skip to content

Latest commit

 

History

History
7 lines (5 loc) · 652 Bytes

unsolicited-dco.md

File metadata and controls

7 lines (5 loc) · 652 Bytes

Unilateral DCO

The draft adds DCO msg which allows route invalidation by the common ancestor node. The DCO message is generated by the ancestor node in response to DAO with I-flag (invalidate previous route flag) set in context to the corresponding target. The I-flag is used as a mechanism so that the target is in-charge of its own invalidation. Having said that, the ancestor node has all the state information needed to generate the DCO unilaterally. Should this be allowed?

Initial Usual DCO Unilateral DCO