I believe that draft-lyon-senderid-core-01 conflicts in a significant aspect with draft-schlitt-spf-classic-02, on which the former depends, and which has also been approved by the IESG to be published as an Experimental RFC.[2] The conflicting part of the Sender-ID specification disrespects the substantial history the SPF specification has outside the IETF. Through its decision, the IESG also ignores SPF's deployed base.[3] And even if the IESG intends to run both of the specifications as an experiment before deciding any further on how to proceed with them, the publication of conflicting specifications is bound to disrupt these experiments.