[Enum] Re: draft-ietf-enum-validation-token-01.txt

Hi Tony,

On 2006/02/16 15:02, Tony Rutkowski <trutkowski@verisign.com> wrote:
> 
> Your very useful token contribution can be
> usefully implemented within what seems the
> universal global architecture and process
> requirement for public ENUM.
> 
> Whoever is running the ENUM EPP bluebox
> will generally require four tokens.

Thank you for sharing your Authentication Architecture diagram.
Some comments/questions:

* Is this for User-ENUM?

* As I read the diagram, you plan to hold NAPTR records in your
  Tier1(b) registry. You don't plan to do "normal" delegations
  based on NS records?

* You're planning to use the data from the ENUM validation to
  feed the E.115 DBs? 

  Here in .at we had long discussions about that as well, and we
  decided against it. In our model, a new ENUM delegations contains

  o The ENUM Token which documents the ownership of the number

  and optionally

  o a domain/number owner contact object which can be set by the registrar.

  If we were to feed our data into a directory assistance DB, we'd
  use the contact object and not the info from the Token.

  For private persons that distinction may be unnecessary. For companies
  this can be an essential feature. E.g. if the numbers of all
  branch offices are managed from the headquarter: Validation is
  done through them, but you still want the local address in the
  phonebook. Or consider a holding with various brands.

* I have some difficulties understanding the roles on the left side
  of your diagram. Could you elaborate a bit on them?

* Concerning the Token from the "E.164 Service Subscriber": Is that
  one digitally signed? If yes, you need some sort of PKI. Who will
  act as the CA in that system?

* About the "referenced service provider": Are you sure you need a
  proactive agreement from that role? 

  Nobody is doing that in the email space. I can point my MX records
  to whomever I want to. I can install email forwards without
  permission from the destination. I can do SIP redirects without
  a token from the destination.

  How much will this also introduce restriction on the SIP service
  hosters? Can a Texan use a SIP provider based in Australia which
  doesn't know a thing about your system?

My plan was to get the token draft into WGLC as soon as possible
as all changes in the last 6 months were mostly cosmentic. 

I'd really like to accomodate any changes you might need. 

So: what are your requirements for the Token specs?

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

_______________________________________________
enum mailing list
enum@ietf.org
https://www1.ietf.org/mailman/listinfo/enum