Two renumbering questions

My ISP is changing upstreams for a variety of reasons around May 18th.

1. I have a /24 SWIPed to me, 205.238.207.0. The ARIN listing doesn't say
it's non-portable, so can I take it with me?

The ARIN db lost all portable/non-portable atributes in the conversion.
Unless folks have gone back and requested they get re-tagged,
portability is unclear from the ARIN db.

[snip]

rather than filtered for being too long? It's right in the middle of the old
upstream's block 205.238.192/18.

If it is a singleton hole in a /18, your most net-friendly action would
be to voluntarily renumber. The provider's most net-friendly action
would be to indicate it was non-portable.

[snip]

(There's other servers elsewhere that won't get renumbered.) If I tell the
Internic that ivan's host number has changed, will that update all the
domains served from it?

Yes, that's the purpose of the HST record. Update the HST and you're
all set.

Joe

> 1. I have a /24 SWIPed to me, 205.238.207.0. The ARIN listing doesn't say
> it's non-portable, so can I take it with me?
The ARIN db lost all portable/non-portable atributes in the conversion.
Unless folks have gone back and requested they get re-tagged,
portability is unclear from the ARIN db.

  Lost as in not displayed to queries or lost as in nobody knows
  what's portable anymore and the canonical data is destroyed?

  I can't imagine the latter is the case, but your assertion is of
  sufficient mangnitude to demand clarification.

  -alan

Joe Provo - Network Architect wrote:

If it is a singleton hole in a /18, your most net-friendly action would
be to voluntarily renumber. The provider's most net-friendly action
would be to indicate it was non-portable.

Why is it so rare to see this type of response?

Because it requires _work_... and as was _just_ noted on the
online-writing list: people are _lazy_.

Cheers,
-- jra

If it is a singleton hole in a /18, your most net-friendly action would
be to voluntarily renumber. The provider's most net-friendly action
would be to indicate it was non-portable.

In case I didn't make it clear in my original question, I figured I'd
probably have to renumber -- I was more wondering if I had the option
to hold on to the old addresses for a little while during the
transition, since the overlap I'll get between the old and new
upstreams will (for a variety of reasons) probably not be very long.