Good Afternoon, As mentioned today in the REGEXT face to face meeting at IETF-100 in Singapore, we have two remaining questions open on the current draft https://datatracker.ietf.org/doc/draft-ietf-regext-epp-fees.
1. <cd> "avail" attribute meaning on partial return of results, see section 3.9 for some additional context. The extension allows servers to choose between returning no results or partial results when a server encounters an issue with one or more of the requested <command>s. The question raised specifically was "Should a partial result set the <cd> "avail" attribute to true or false". The intent of the draft was to return "avail=0" on partial (there was some failure), but some implementations have interpreted it as "avail=1" (some data returned). What do people think? 2. Appropriate level of <fee:class>, see section 3.7 for more details. There has been an ongoing discussion on moving the <class> element to the object level (i.e. at the <cd> level versus the <command> level). Currently the draft has this at the <command> level but I do believe in the merits of the argument that in reality/practice <class> is defined at the domain object level and not the command level, so unless there are arguments to keep it at the command level the next version will move this to the object, <cd>, level. After comments have been received and document updated accordingly, we will ask for WGLC. Thanks Roger
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
