True - but 95% of the domains that take longer than 5 days are NOT NSI.
They're actually pretty good about it (believe it or not).
That aside - I'll see what I can stir up over here ;)
"Derek J. Balling" wrote:
>
> OK, y'see from where I sit, considering NSI being who they are, if
> you let them get away with 2-3% of the domains taking longer than the
> "published maximum spec", they'll keep doing it, whereas if you push
> the issue with NSI-Registry, and nip it in the bud before it becomes
> "NSI-Registrar's standard practice", then everyone is a lot better
> off for it... :-/
>
> D
>
> At 6:16 PM -0400 8/17/00, Charles Daminato wrote:
> >Once we've placed a transfer command via RRP there's nothing we can do
> >after that. Either the transfer goes through, or it does not. It's rare
> >that this takes longer than 5 days - some exceptions seem to be transfers
> >from registrars.com If it becomes an issue (i.e. more than 2 or 3% of our
> >transfers, which it currently seems to be) we will definitely push the
> >issue with NSI Registry.
> >
> >"Derek J. Balling" wrote:
> >>
> >> At 4:22 PM -0400 8/17/00, Charles Daminato wrote:
> >> >There shouldn't be any problems - domains can take up to 9 days we've
> >> >noticed, although RRP API states 5 days (go figger).
> >> >
> >> >I'd wait two more days and see what happens :)
> >>
> >> This has been mentioned before but I never saw a satisfactory answer:
> >>
> >> If the spec says 5 days, why isn't SRS, as the "winning" registrar,
> >> pushing the issue on Day Six?
> > >
> > > D
> >
> >--
> >
> >Charles Daminato
> >OpenSRS Support Manager
> >[EMAIL PROTECTED]
--
Charles Daminato
OpenSRS Support Manager
[EMAIL PROTECTED]
