[enum-wg] Questions concerning CRUE

Jim,

yesterday's session was bit tight in terms of time for questions, thus
here they come on the list. There are a few points where I'm not sure I
understand the CRUE proposal, so please correct me if I got this wrong:

* The registry will not provision any CRUE records just by themselves.

* The main difference between CRUE entries and normal delegations are:

  + CRUE records are requested by the carrier, and not the end-user.

  + CRUE records are validated by public Ofcom block allocation data,
    vs. whatever you do for normal user-enum

  + CRUE records use NAPTRs in the registry vs. normal delegations
    based on NS records in the Tier1 zone

* From the point of the ENUM client which just cares about NAPTR records, 
  there is no difference between Numern->URI mappings provided by 
  CRUE records and normal user-enum NAPTR records.

Some more questions:

* You said that the registry makes no assumptions on the reachability
  of the SIP URIs contained in the CRUE record. What about the carriers
  interested in CRUE? Did you talk to them about their plans?

  One of the reasons we started the I-ENUM trial here was the fact that
  some of the operators refused to run open servers and wanted detailed
  control on whom they peer with.

* What about ported numbers? From what I know about the .uk system,
  Ofcom doesn't hold information about those.

* CRUE entries will be provisioned by the number-owning carrier: Will
  they have to send a CRUE request for every single number, or will
  there be a block-provisioning interface? If yes, will that make use
  of the NAPTR regexp feature to have identical NAPTR records for 
  whole blocks?

Thanks,

/ol
-- 
< Otmar Lendl (lendl at nic.at) | nic.at Systems Engineer >