[v6ops] Operational guidelines for a company/organization IPv6 address scheme supplemental to RFC5157

["Marksteiner, Stefan" <[e-mail]>]

Hi Folks,

RFC5157 presents hazards of sequentially numbering IPv6 networks and technical means (like CGAs and privacy extensions) to mitigate them. Unfortunately these mitigation methods may be deemed difficult to handle for administrators (SEND may be too complicated to implement, PEs bring difficulties to keep track of IP addresses). Therefore there may be demand for an addressing scheme (rather than a technical method) that makes IPv6 addresses easy to predict for tech staff but difficult to do so by outsiders, building a low-end supplement for the methods mentioned in RFC5157.

What I have in mind is an simple mental arithmetic operation, which generates an address out of a company fixed part plus a sequential number for host. Alternatively a Hash-Operation consisting again of a secret organisational plus a sequential host number. The first requires the scheme to be slightly different in every organisation in order to have a negative impact on IPv6 scanning from external sources, the second is more secure but requires an internal web site or smartphone app in order for field engineers to calculate an address out of the sequential information.

My question is, in your opinion, would this be worthwhile to be formulated as an ID an be drafted or does this idea sound absurd?


Cheers,

Stefan