1 / 20

Agenda Marc Blanchet and Chris Weber July 2011

Agenda Marc Blanchet and Chris Weber July 2011. IRI WG IETF 81. Note Well. Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context

walt
Télécharger la présentation

Agenda Marc Blanchet and Chris Weber July 2011

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Agenda Marc Blanchet and Chris WeberJuly 2011 IRI WGIETF 81

  2. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: • the IETF plenary session, • any IETF working group or portion thereof, • the IESG or any member thereof on behalf of the IESG, • the IAB or any member thereof on behalf of the IAB, • any IETF mailing list, including the IETF list itself, • any working group or design team list, or any other list • functioning under IETF auspices, • the RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 3978 (updated by RFC 4748) and RFC 3979 (updated by RFC 4879). Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 3978 (and RFC 4748) for details. A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in Best Current Practices RFCs and IESG Statements. A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public.

  3. AGENDA • Scribe selection and Agenda bashing • WG Status / Overview • Guidelines and Registration Procedures for New URI/IRI Schemesdraft-ietf-iri-4395bis-irireg • Processing potentially invalid URI and IRI References draft-reschke-ref-parsing-00 • Guidelines for Implementers of Internationalized Resource Identifiers draft-weber-iri-guidelines-01 • Internationalized Resource Identifiers (IRIs) draft-ietf-iri-3987bis • Open Floor • Closing / Next Steps

  4. WG Status - Drafts • IRIs: draft-ietf-iri-3987bis-05 • Reviewing test results and IRI display in past weeks • Individuals say ‘not normative enough‘ for HTML5 • Which bits exactly? • Future direction? • New Schemes: draft-ietf-iri-4395bis-irireg-02 • Not much review in the past weeks • Open issues closed this week • New draft published this week • Ready for Last Call?

  5. WG Status - Drafts • Parsing Invalid: raft-reschke-ref-parsing-00 • Using RFC3986 regexp for parsing invalid URIs • Define parsing of any reference • Define resolution against any base reference • IRI Guidelines: draft-weber-iri-guidelines-01 • Pre-processing strings for IRI parsing • Define parsing strings into IRI components • Define limited scheme-specific post-processing

  6. WG Status - Drafts • Parsing URLs: draft-abarth-url-01 • Define observed parsing behavior across browsers

  7. WG Status – Next Milestones • Provide a reference suitable for HTML5 by adopting or merging new drafts (Barth, Reschke, Weber)? • 3987 IRIs – re-charter based on new drafts, LC when? • 4395 Scheme registration - LC when?

  8. AGENDA • Scribe selection and Agenda bashing • WG Status / Overview • Guidelines and Registration Procedures for New URI/IRI Schemesdraft-ietf-iri-4395bis-irireg • Processing potentially invalid URI and IRI References draft-reschke-ref-parsing-00 • Guidelines for Implementers of Internationalized Resource Identifiers draft-weber-iri-guidelines-01 • Internationalized Resource Identifiers (IRIs) draft-ietf-iri-3987bis • Open Floor • Closing / Next Steps

  9. RFC4395bis (IRIREG) • Open those slides… • Most issues closed this week • More comments/feedback? • Last Call?

  10. AGENDA • Scribe selection and Agenda bashing • WG Status / Overview • Guidelines and Registration Procedures for New URI/IRI Schemesdraft-ietf-iri-4395bis-irireg • Processing potentially invalid URI and IRI References draft-reschke-ref-parsing-00 • Guidelines for Implementers of Internationalized Resource Identifiers draft-weber-iri-guidelines-01 • Internationalized Resource Identifiers (IRIs) draft-ietf-iri-3987bis • Open Floor • Closing / Next Steps

  11. Parsing Invalid References • draft-reschke-ref-parsing-00 • Julian Reschke’s slides

  12. AGENDA • Scribe selection and Agenda bashing • WG Status / Overview • Guidelines and Registration Procedures for New URI/IRI Schemesdraft-ietf-iri-4395bis-irireg • Processing potentially invalid URI and IRI References draft-reschke-ref-parsing-00 • Guidelines for Implementers of Internationalized Resource Identifiers draft-weber-iri-guidelines-01 • Internationalized Resource Identifiers (IRIs) draft-ietf-iri-3987bis • Open Floor • Closing / Next Steps

  13. IRI Guidelines • draft-weber-iri-guidelines-01 • Problem statement • HTML5 needs a stable and normative reference for parsing • 3987 was said to be ‘not normative enough’ • 3987 does not match observed browser behavior?

  14. IRI Guidelines • Proposal • A standards-track document that… • Defines pre-processing steps • Defines steps for parsing arbitrary strings into IRI components • Defines limited scheme-specific post-processing • Problems solved • A URL parsing reference for HTML5

  15. AGENDA • Scribe selection and Agenda bashing • WG Status / Overview • Guidelines and Registration Procedures for New URI/IRI Schemesdraft-ietf-iri-4395bis-irireg • Processing potentially invalid URI and IRI References draft-reschke-ref-parsing-00 • Guidelines for Implementers of Internationalized Resource Identifiers draft-weber-iri-guidelines-01 • Internationalized Resource Identifiers (IRIs) draft-ietf-iri-3987bis • Open Floor • Closing / Next Steps

  16. RFC3987bis (IRIs) • Future goals? • Provide normative parsing algorithm with error handling? • Or reference Barth, Reschke, Weber’s draft? • If so, merge these draft efforts and remove redundant bits from 3987bis?

  17. RFC3987bis (IRIs) • Do we agree on the definition of an IRI? • Do current implementations agree with 3987? • Do they agree with 3986? • Issue #5: Move BIDI IRIs to separate document?

  18. AGENDA • Scribe selection and Agenda bashing • WG Status / Overview • Internationalized Resource Identifiers (IRIs) draft-ietf-iri-3987bis • Guidelines and Registration Procedures for New URI/IRI Schemesdraft-ietf-iri-4395bis-irireg • Processing potentially invalid URI and IRI References draft-reschke-ref-parsing-00 • Guidelines for Implementers of Internationalized Resource Identifiers draft-weber-iri-guidelines-01 • Open Floor • Closing / Next Steps

  19. Other topics / open mike • Discuss, Comments, Questions, …

  20. Thank you

More Related