>
> >>> Except there really is no vendor lock anymore. It is
> >>> possible to automate the entire renumbering process. If
> >>> there are spots where it is not automated then they should
> >>> be found and fixed.
> >>>
> >> It's not possible to automatically renumber firewall configurations in
> >> different administration domains (quite deliberately so), and you
> >> can't take your mail reputation with you (at least not completely).
> >>
> >
> > Actually it is. You just are not willing to do it. It is
> > 100% possible to do this automatically. It just requires
> > the chains of trust to be setup.
> >
> you seem to be thinking that this is a purely technical problem. it's not.
>
> and there are valid reasons for keeping humans in the loop, and slowing
> things down, when trust is involved.
Actually I doubt that there really are valid reasons other
than to initiate the change. You can send the notification
of change automatically. It can be acknowledge automatically.
Whether it is approved at the other site automatically
doesn't matter. You can even send reminders automatically
only escalating to humans when there is a failure to respond
after a period of time.
We automate similarly trust relationships all the time.
I've added/removed prefix <value>.
Please update your firewall to reflect this.
This is not a hard message to send automatically. To process
automatically. To acknowledge that the change has been
performed automatically. It's a update to a existing
relationship.
Mark
> Keith
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED]
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf
