The safest approach is to use network statements. When you do so, you know exactly what routes are going to be redistributed. However, that only works for static situations where you know the routes in advance. When you don't know the precise routes that you will be learning from your IGP, redistribution (with appropriate route-maps) is the approach to use.
So, in a nutshell, the choice depends on your situation.
just an additional remark to the post of Paresh. In case you talk about the internet, then you also need to take into account two requirements coming from the ISPs. First any announcement should be /24 or larger, because many large ISPs discard smaller networks anyhow. Second many ISPs use route flap dampening. This means if you withdraw-announce-withdraw-announce and so on, your networks will be dampened (i.e. not used and not announced) within many ASs. So you will have connectivity problems. This is the reason to use something like:
router bgp 65000
network 22.214.171.124 mask 255.255.0.0
ip route 126.96.36.199 255.255.0.0 Null0 250
which will provide the required stability in IP routing.
In case you use the EGP to f.e. an MPLS VPN you might want to announce any internal network - as fast as possible - because you use the EGP internally within your own VPN.
As Paresh wrote: it depends on your requirements - within your AS you can do what you want, when peering with another AS you have to take into account their rules as well.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...