Everything Old is New Again Leslie Daigle Random

  • Slides: 16
Download presentation
Everything Old is New Again Leslie Daigle Random IETF participant May 2012

Everything Old is New Again Leslie Daigle Random IETF participant May 2012

Overview • Microcosm/macrocosm and evolution • Cases in point • Take aways

Overview • Microcosm/macrocosm and evolution • Cases in point • Take aways

Microcosm: A Step in Managed Evolution Change Stimulus Uptake Scalability size diversity Integration architecture

Microcosm: A Step in Managed Evolution Change Stimulus Uptake Scalability size diversity Integration architecture deployed reality

Macrocosm: Evolution Never Sleeps Change Stimulus 1 Change Stimulus 2 Uptake … Change Stimulus

Macrocosm: Evolution Never Sleeps Change Stimulus 1 Change Stimulus 2 Uptake … Change Stimulus N Time

Evolution & Engineering • Requirements overlap and coalesce • One really good idea can’t

Evolution & Engineering • Requirements overlap and coalesce • One really good idea can’t work if it doesn’t fit the bigger picture

Case in point: Uniform Resource Names • Change stimulus – need names, not just

Case in point: Uniform Resource Names • Change stimulus – need names, not just locations, for applications infrastructure • Integration – naming as scheme within URI syntax – discovery of resolution services • Scalability – Dynamic Delegation Discovery Service – Current implementation choice: DNS infrastructure used for discovery of resolution services

Case in point: URN uptake & follow on • DDDS generalized, and applied elsewhere

Case in point: URN uptake & follow on • DDDS generalized, and applied elsewhere – ENUM – IRIS DREG (domain name whois replacement) – Project Liberty metadata discovery service • Names – resource names for IANA registrations built on URNs – XML resource names – ISBNs, ISSNs

Update: URNBIS WG • APP Area WG chartered to – Update the syntax to

Update: URNBIS WG • APP Area WG chartered to – Update the syntax to conform to URI spec – Update registration procedures document – Consider URI fragments (#<fragment>) for URNs • Much of the interest and impetus has come from the bibliographic community – not applications infrastructure

URNBIS documents • Current WG documents – draft-ietf-urnbis-rfc 2141 bis-urn-02 – draft-ietf-urnbis-rfc 3044 bis-issn-urn-00

URNBIS documents • Current WG documents – draft-ietf-urnbis-rfc 2141 bis-urn-02 – draft-ietf-urnbis-rfc 3044 bis-issn-urn-00 – draft-ietf-urnbis-rfc 3187 bis-isbn-urn-02 – draft-ietf-urnbis-rfc 3188 bis-nbn-urn-03 – draft-ietf-urnbis-rfc 3406 bis-urn-ns-reg-02

Whitepages and the Global Directory • No such thing as a global whitepages directory;

Whitepages and the Global Directory • No such thing as a global whitepages directory; no solution that – was scalable, addressing local & global requirements – could be integrated • Various efforts – X. 500, LDAP, etc • whois – originally defined in RFC 954 – specifically for declaring nodes in the arpanet

Change Stimuli for whois • Need something with modern security features – access control

Change Stimuli for whois • Need something with modern security features – access control – authentication • Need something that supports the world’s names – i. e. , more than just ascii • Need something that does this consistently – I. e. , interoperable, around the globe

Case in point: IRIS • Change stimulus – need access control, internationalization and better

Case in point: IRIS • Change stimulus – need access control, internationalization and better management for whois • Integration – reuse of available components (XML, application transports) – framework for expressing queries/responses defining a service • as opposed to specific schema or attribute semantics, with open-ended query language • Scalability – local access and language rules apply – basis for other registries’ information services

Oooops. . .

Oooops. . .

Update: WEIRDS • Change stimulus – need standard form for accessing resource registration data

Update: WEIRDS • Change stimulus – need standard form for accessing resource registration data with security, support for more than ascii • Integration – reuse: RESTful web services – for numbering (RIR) and naming (DNS) resources • Scalability – Web Extensible Internet Registration and Data Service

WEIRDS Status • Chartered May 15 2012, APPS Area – Chairs: Olaf Kolkman, Murray

WEIRDS Status • Chartered May 15 2012, APPS Area – Chairs: Olaf Kolkman, Murray Kucherawy – weirds<at>ietf. org • Starting docs under consideration – – – draft-designteam-weirds-using-http draft-kucherawy-weirds-requirements draft-sheng-weirds-icann-rws-dnrd draft-hollenbeck-dnrd-ap-query draft-newton-et-al-weirds-rir-query

To Take Away • What we have learned about evolving from our protocols –

To Take Away • What we have learned about evolving from our protocols – All universes expand • the Internet is a long way from host requirements (RFC 1123), when the world was more uniform • the Internet architecture adapts – Interconnections between network infrastructure components • are to be valued • require careful evolution (micro/macrocosm) – Evolution cannot work only on microcosm in isolation