Re: EPP host renames

For host:info? There's nothing explicit in the child elements describing 
a client that is associated with the host object.

   Example <info> response:

    S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
    S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
    S:  <response>
    S:    <result code="1000">
    S:      <msg>Command completed successfully</msg>
    S:    </result>
    S:    <resData>
    S:      <host:infData
    S:       xmlns:host="urn:ietf:params:xml:ns:host-1.0">
    S:        <host:name>ns1.example.com</host:name>
    S:        <host:roid>NS1_EXAMPLE1-REP</host:roid>
    S:        <host:status s="linked"/>
    S:        <host:status s="clientUpdateProhibited"/>
    S:        <host:addr ip="v4">192.0.2.2</host:addr>
    S:        <host:addr ip="v4">192.0.2.29</host:addr>
    S:        <host:addr ip="v6">1080:0:0:0:8:800:200C:417A</host:addr>
    S:        <host:clID>ClientY</host:clID>
    S:        <host:crID>ClientX</host:crID>
    S:        <host:crDate>1999-04-03T22:00:00.0Z</host:crDate>
    S:        <host:upID>ClientX</host:upID>
    S:        <host:upDate>1999-12-03T09:00:00.0Z</host:upDate>
    S:        <host:trDate>2000-04-08T09:00:00.0Z</host:trDate>
    S:      </host:infData>
    S:    </resData>
    S:    <trID>
    S:      <clTRID>ABC-12345</clTRID>
    S:      <svTRID>54322-XYZ</svTRID>
    S:    </trID>
    S:  </response>
    S:</epp>


However under statuses it says:

- linked
The host object has at least one active association with another object, 
such as a domain object. Servers SHOULD provide services to determine 
existing object associations.

So there's a directive to provide that information you are looking for.  
However its a SHOULD not a MUST - 10 years later I'm leaning towards a 
MUST :-)

I'm not sure it really needs to be done in the host:info command for 
example: if I process a delete command against a host and it fails as a 
result of an existing association, then data about that existing 
association can be part of the error response.  A list of all 
associations with even a single host object could be a massive 
response.  More than one way to solve for this.

-M

On 2012-12-20 3:02 AM, InterNetX - Volker Janzen wrote:
> Hi,
>
> On 12/19/2012 08:07 PM, Michael Young wrote:
>
>> Currently registrar a contacts registrar b and complains. Registrar b
>> disassociates the host object regardless of the fact the registrant
>> went silent.
> if you want to be able to reach the registrar b, a host:info command has
> to tell you which domains are connected to your host object. Is this
> behaviour in the RFC?
>
>
> Volker Janzen
> Team Entwicklung
>

_______________________________________________
provreg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/provreg