RE: More Private Comments

["Hollenbeck, Scott" <shollenbeck@verisign.com>]

> -----Original Message-----
> From: Daniel Manley [mailto:dmanley@tucows.com]
> Sent: Friday, December 21, 2001 10:12 AM
> To: Hollenbeck, Scott
> Cc: 'ietf-provreg@cafax.se'
> Subject: Re: More Private Comments
> 
> 
> thanks for posting this Scott.  The only other suggestion we 
> have would 
> be to include a "type" attributes to the <polledMsg> tag.  
> I'm not sure 
> if EPP could define a set of types since EPP only defines 
> that transfers 
> must generate messages.  So possibly a pattern like <polledMsg 
> type="transfer:domain" id="123">Transfer requested</polledMsg>.  This 
> would allow parsing clients to know how to parse the XML in <resData> 
> without having to pre-parse it beforehand.

I don't believe we could come up with a definitive set of types, though it
might be possible to say that the value of the "type" attribute is a
combination of the EPP command that caused the message and the namespace of
the object that was involved.  That means it won't be something that can be
validated by the XML parser, but it might still be useful.

> Also, I was wondering if poll in the EPP documents (this would also 
> apply to futur push implementations, if any) should be 
> further defined 
> like this:
> 
> "An EPP server MUST generate queued messages or notifications to the 
> registrar if an object owned by the registrar is affected or changed 
> without the registrar's invovlement."  (or something of the sorts)

OK, I could add text to the <poll> description to get that message across.
I don't think we can use words like "registrar" or "owned", but I understand
the intent of the suggestion.

-Scott-