on page NUMBER_TOKEN of the rfc that set this up it's rfc NUMBER_TOKEN dated way back even before that uh NUMBER_TOKEN. uh this this one is from NUMBER_TOKEN rfc NUMBER_TOKEN page NUMBER_TOKEN of that rsc of our that rfc very clearly states um NUMBER_TOKEN and then any no any bits and it says internal host loopback address addresses of this form must not and you know this is in the formal rfc language so all capitals must all capitals not appear outside a host um and that explains why i did a serious double take and i really did check the date to be certain it didn't say april NUMBER_TOKENst when last week i encountered an official ietf standards track proposal titled unicast use of the formerly reserved NUMBER_TOKEN-NUMBER_TOKEN
NO_SEGMENT_TOKEN