Re: [ietf-provreg] Unique identifiers for Contact

[Andre Marais <andre@flame.co.za>]

Hi Joe,

> > Shouldn't there be a command that allows for identifier generation on
> > the server side which would eliminate this type of problem?
> 
> Which identifier do you mean?

As per the example from draft-ietf-provreg-epp-contact-06:

  C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
  C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
  C:     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  C:     xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
  C:     epp-1.0.xsd">
  C:  <command>
  C:    <check>
  C:      <contact:check
  C:       xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
  C:       xsi:schemaLocation="urn:ietf:params:xml:ns:contact-1.0
  C:       contact-1.0.xsd">
  C:        <contact:id>sh8013</contact:id>
  C:        <contact:id>sah8013</contact:id>
  C:        <contact:id>8013sah</contact:id>
  C:      </contact:check>
  C:    </check>
  C:    <clTRID>ABC-12345</clTRID>
  C:  </command>
  C:</epp>

The identifier I was referring to was the contact:id element as shown
above. This field should be server-unique according to the spec, and as
explained could cause problems in high-volume cases.

> I think the only identifiers mentioned in the base spec are transaction 
> identifiers. Collisions between clTRIDs used by different registrars 
> are legal; svTRIDs are generated by the server in all cases, and hence 
> making them unique should be straightforward.

Agreed, but see above.

Regards,
Andre

-- 
Reading, after a certain age, diverts the mind too much from its 
creative pursuits. Any man who read too much and uses his own brain 
too little falls into lazy habits of thinking.
 - Albert Einstein.

-----------------------------------------------------------------------
LEGAL DISCLAIMER:
The views or representations contained in this message, whether express
or implied, are those of the sender only, unless that sender expressly
states them to be the view or representations of an entity or person,
who shall be named by the sender and the sender shall state to
represent. No liability shall otherwise attach to any other entity or
person.
-----------------------------------------------------------------------

This is a digitally signed message part