-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> If we're forced to break backward compatibility then we'll have to
> evaluate whether the OID needs to change. Currently, I think the answer
> would be no; fairly soon, I think the answer would be yes. However I
> don't think it would be a big deal if we needed to burn a few codepoints
> in an ABFAB mechanisms oid arc. I also think it matters very little
> where that OID arc lives--IETF or not.
So basically your vote is on an enterprise arc. I'm not sure I
understand the reasons why abfab has requirement that differ so
much from any other IETF protocol where protocol numbers are
typically allocated on publication of the RFC.
Cheers Leif
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk0+3VYACgkQ8Jx8FtbMZnf8TACgoOWK1msFa1YikKESyyVAdPM7
EIYAoKGK1GRwtAUJmOmgwlSrRvPtDWCa
=GCna
-----END PGP SIGNATURE-----
_______________________________________________
abfab mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/abfab
