1 / 8

draft-lewis-peppermint-enum-reg-if-01.txt

draft-lewis-peppermint-enum-reg-if-01.txt. Edward Lewis PEPPERMINT BoF IETF 70. Why it is. Meant as placeholder for a requirements draft -00 contained reversed engineered requirements for an in-house effort plus a harangue on EPP

lavinia-augustus
Download Presentation

draft-lewis-peppermint-enum-reg-if-01.txt

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. draft-lewis-peppermint-enum-reg-if-01.txt Edward Lewis PEPPERMINT BoF IETF 70 ed.lewis@neustar.biz

  2. Why it is • Meant as placeholder for a requirements draft • -00 contained reversed engineered requirements for an in-house effort plus a harangue on EPP • -01 is a repeat, without edits to include comments the first time around (sorry) ed.lewis@neustar.biz

  3. What it is • Built from experience • Provisioning/Registration Interface • Application layer • Presentation layer • Session layer • Transport layer • Resolution Interface • How it deals with, basically, DNS ed.lewis@neustar.biz

  4. What We Based Our Ideas On Provisioning Interface Resolution Interface TN->URI Zone Ups Provisioning/ Registry Op Supt Syst DNS "Front End" XML XML BEEP BEEP TLS TLS ed.lewis@neustar.biz

  5. Why mention EPP? • It's an obvious alternative • We decided against it • But we didn't want to forget about it • We anticipate a discussion about that choice to be held at some point ed.lewis@neustar.biz

  6. Comments about -00 • It shouldn't dive in to the EPP debate • I agree, it'll come out sooner or later • If this document was to state our experience • The intent is a widely reviewed reqts doc, but we had to start somewhere • Why not from our running code? ("Our" = $editor's team) ed.lewis@neustar.biz

  7. Two archived comments • I thought I sent these URLs out, but I don't see my message in the archive: • http://www1.ietf.org/mail-archive/web/peppermint/current/msg00022.html • http://www1.ietf.org/mail-archive/web/peppermint/current/msg00058.html • Mentioned to show I am not ignoring the discussion ed.lewis@neustar.biz

  8. Other Discussion? • I'm done presenting ed.lewis@neustar.biz

More Related