Subject: [saag] SIDR status

From: Sandra Murphy <[email-masked]>
Date: Thu, 30 Mar 2017 12:39:57 -0400

SIDR did not meet at this IETF, but status and discussion in SIDROPS 14:50-16:20 Tuesday Afternoon session II

WG Highlights:

dewindling down to a precious few remaining work items; six drafts transferred to the new sidrops wg

WG Status Summary

9 drafts in RFC Editor queue

drafts remaining: 1 post IESG, 2 expired to be renewed, 1 wglc requested, 1 waiting resolution of AD comments, 1 waiting resolution of AD query, 1 blocked by idr draft progress.

There was a discussion at the sidrops meeting about that last draft. The bgpsec-protocol (presently in RFC Editor queue) has a normative reference to the idr wg's extended messages drafts, which has been returned to the idr wg for more work.

Various opinions were expressed as to whether the delay was acceptable and what we could do to the bgpsec draft to remove the block if the delay was not acceptable, etc.

One option for dealing with a bgpsec update that would exceed the maximum size was to drop the bgpsec signatures.  One operator was concerned that this was a “fail open”.  No decision was made, discussions will continue.

—Sandy