Or you can all just agree to use a private value then once you are
happy it all works apply for a the final value. This allows you
to fiddle with wire format etc. without permanently tainting a
assigned value if you need to change wire format. Grab a new private
value if you change the wire format etc.
65499 looks good to use and as you have a prefix it shouldn't cause
problems for anyone else. It is just a opaque blob to nameservers.
It shouldn't be that hard to have something like this in a config
file.
smime-type = 65499;
masterfiles get
<key>.<label>.mail.domain.example. TYPE65499 \# <length> <hexstring>
I'm done this sort of thing a number of times. DLV started out as
a private value. When a code point was assigned we just changed
the code to use that value. Yes, there will still be some instances
of named with the old code point in them even today but it doesn't
matter. If you want to use dlv today you will upgrade them.
Named uses some private values.
DNSCOOKIE started out as a private EDNS option and now has a assigned
value.
SPF could have moved if people were not stuborn about it. Oh dear
we might get a little extra spam while we transition if we don't
call both types. Totally bogus "interoperability" arguments. Flip
the type and be done.
Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: [email protected]
_______________________________________________
dane mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dane
