90 likes | 181 Views
IRIS AREG Draft. draft-ietf-crisp-iris-areg versions 07 & 08. Summary. Two new drafts diff between versions 06 & 07 diff between versions 07 & 08 URI Resolution. IRIS AREG. Two more drafts published draft-ietf-crisp-iris-areg-07 draft-ietf-crisp-iris-areg-08.
E N D
IRIS AREG Draft draft-ietf-crisp-iris-areg versions 07 & 08
Summary • Two new drafts • diff between versions 06 & 07 • diff between versions 07 & 08 • URI Resolution
IRIS AREG • Two more drafts published • draft-ietf-crisp-iris-areg-07 • draft-ietf-crisp-iris-areg-08
diff between 06 and 07 – part 1 • <name> element and name searches for networks and ASNs are back • <findASNByNumber> search is in, • with specificity • AS query out (not needed) • Added <language> element to <findOrganizations> and <findContacts> • Client passes names unchanged, • Implementation decides about case-sensitivity
diff between 06 and 07 – part 2 • 'closest-match' specificity query is out • covered by less-specific query with 'allowEquivalences' set to true • <beginsWith> and <endsWith> back into <findOrganizations>, <findAutonomousSystemsByName>, <findNetworksByName>, <findContacts> • Added <findByContact> search for ASNs, networks, organisations by contact. • Added <findNetworkBySpecificity> search • parentage relations
diff between 06 and 07 – part 3 • Changed formal XML syntax section to match the other changes. • <commonName> in, <firstName>, <middleName>, and <lastName> out in <contact> result. • <eMail> element in <organization> result. • Changed URI resolution.
diff between 07 and 08 • <findNetworksByNameServer> search added • split references into normative and informative • Examples added for specificity as an appendix • fixes in example requests and responses section • fixes in formal XML
URI Resolution The client SHOULD start every query from the IRIS server iris.nro.net and follow the referrals to find the authoritative server to actually query. • What will IESG think about hardwiring a DNS name into the RFC?