[Ietf-not43] IRIS Open Issues

[Andrew Newton]

The following are the items from the IRIS open issues presentation given
Wednesday during the working group meeting.  Please provide comments if
you have them.

AREG
o AREG has only been updated according to a couple of directed comments
on the list.
o Does not yet attempt to conform to
draft-ietf-crisp-internet-resource-number-req
     - Just a time/bandwidth issue

Resolutio Methods
o DREG
     - Defines top-down and bottom-up DNS tree walking
     - Good enough?
o AREG
     - Top-down and bottom-up reverse DNS tree walking
     - Given that reverse DNS tree does not always accurately represent
network boundaries, should we think about others?

Misc. Changes
o Side-effects of comments on -03
     - <iris:serializedEntity> goes away due to redefinition of 
<iris:entity>
     - Replaced by <iris:entity> with null 'authority' attribute content
o According to RFC 2396, IETF assigned URI's cannot have dashes
     - Therefore “iris-beep” URI scheme is now “iris.beep” according to
common practice

Host in DREG
o One implementer has noticed that the ipv4/v6 address elements are the
only ones inside a container.
o This is not consistent with the rest of <dreg:host> children.

Status in Domain
o New change to <sequence> forces server to sort them before sending them.
o Maybe it should be <choice minOccurs='0' maxOccurs='unbounded'>
     - With the addition of a boolean valued 'current' attribute on
<appliedDate>, this allows servers to convey the history of the domain
if they want.
     - Or simply specify that only one type of status element be used
(must be expressed in words... not possible in XML Schema).

(NOTE: I'll try to cover this in more detail in a separate email since
it is really asking for a choice.)

Draft Mechanics
o All four drafts need to have references split into normative/informative.
o Proper registration for the URN's in the 'ietf' NID.
o Otherwise ID-nits compliant.

-andy