The Problem STD action in RTG area requires implementations Certain code-point ranges use “STD action” policy Implementers can’t get codes from IANA, pick next available (X)---BAD! Risk of collisions when X is allocated by IANA or another early implementation uses it Seen this problem with RSVP FLOWSPEC and SENDER_TSPEC C-Types IDR: new BGP spec uses STD action as the policy |