>-----Original Message----- >From: Jared Mauch [mailto:ja...@puck.nether.net] >Anyone can write an informational rfc. See apr 1 as an example. One can easily >write up what they do, or survey responses. You can then follow the feedback >from your request.
That is exactly my point - if /126s are the "industry preferred" approach, I fail to see why it hasn't been codified in an (atleast) information RFC. Once submitted in this fashion, it could be further reviewed and perhaps even be updated later-on to be a proposed standard. ( any "directive" documentation would need to be PS as it is changing a PS. ) >Jared Mauch Thanks! /TJ _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
