> The response I got back was that this was impossible since ISPs require an
> announcement of the /16 the /19 would come from. I have done work with ISPs
> before (and have read the NANOG list for many years) but haven't heard of
> such a requirement nor can I find any standards that indicate th
> >
> > Hi-
> >
> > I'm working on a project within a large corporation and asked
> > their network folks about getting a /19 from one of their
> > /16s. I wanted it to avoid NAT and any possible overlapping
> > from using RFC1918 addresses. This project gets connected to
> > the internet
> -Message d'origine-
> De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De
> la part de Eric Pylko
> Envoyé : lundi 5 juillet 2004 22:02
> À : [EMAIL PROTECTED]
> Objet : Announcing a /19 from a /16
>
>
> Hi-
>
> I'm working on a p
Hi-
I'm working on a project within a large corporation and asked their network
folks about getting a /19 from one of their /16s. I wanted it to avoid NAT
and any possible overlapping from using RFC1918 addresses. This project
gets connected to the internet at different times throughout the yea
