How to compare one time pad security and efficiency with AES? It seems that the minimal size of Pseudorandom permutation (PRP) output is $128$ bits. In general, I'd like to see if there's any minimal size of the output of pseudorandom function (PRF) as well? for instance can we set the output size of PRF to 32 or 40 bits. 

Below, I'm trying to explain the question with an example. 



Let $k_i$ be secure random key. I've a message $m$ of 32-bit. I want to encrypt it in two different ways:


Using output of a pseudorandom function (PRF) as a one time pad: I do the following: 

a) $PRF_{k_1}(0)=a$, 

b) $c_1=a \cdot m$. 
Using a Pseudorandom permutation (PRP): 

a) $c_2=PRP_{k_2}(m)$




Question 1: What is the minimal size of $c_1$? Can we set the output size of PRF to 32 bits, so the size of $c_1$ would be the same? 

Question 2: what is the minimal size of $c_2$? Am I right it is at least 128 bits?

Question 3: If the answer to both questions is positive, then how can we compare the security and efficiency of the above two schemes with each other? 



Please kindly let me know if my question is not clear, etc instead of down voting it; and I'll address your comments.
Answer 1:  If you are going to use a "one time pad", then $c1$ must be exactly the same size as $m$, so $c1$ must be 32 bits.  (Note:  Using a PRF and evaluating with the input of 0 is not a one-time pad.  It might be equivalent if you change $k_i$ every time, but then why bother with the PRF when you could use $k_i$ directly?)

Answer 2:  Since you specific it as a PRP (pseudorandom permutation), $c2$ must be 32-bits.  With a permutation, the size of the input matches the size of the output.  A PRP pseudorandomly maps each element of the possible input set to a single item in the output set.  So as with the first, $m$ and $c$ must be exactly the same size.  

Answer 3: There isn't sufficient information about the rest of the system or usage to really comment on their security with the exception to say:  trying to make a "one-time pad" from other function almost always fails and anything that has only a 32-bit input can probably be trivially brute forced.