21 November 2002IETF 55 - Atlanta, GA, USA1 The Internet Standards Process For the SPEECHSC Work Group Eric Burger

Slides:



Advertisements
Similar presentations
Whos who in the IETF Zoo? Geoff Huston Executive Director, Internet Architecture Board.
Advertisements

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.
Lesson 16 Enhancing Documents
Open Pluggable Edge Services (opes) 62 nd IETF Meeting Minneapolis, MN, USA.
OASIS document rules Nigel Shaw Eurostep Limited.
Editor Intro IETF59 Seoul, ROK This Session  Please let me know if this talk meets your expectations your needs  recommendations for improvement.
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.
Draft-loughney-what-standards-01.txt IETF 59 NEWTRK WG Presented by Spencer Dawkins.
WG RAQMON Internet-Drafts RMON MIB WG Meeting Washington, Nov. 11, 2004.
November 2011IETF TRILL WG1 TRILL Working Group TRansparent Interconnection of Lots of Links Mailing list: Tools site:
MPTCP – Multipath TCP WG Meeting Toronto, IETF-90, 21 st July 2014 Philip Eardley Yoshifumi Nishida 1.
Network Virtualization Overlays (NVO3) NVO3 Meeting, IETF 88, Vancouver Benson Schliesser Matthew Bocci
MASS / DKIM BOF IETF – Paris 4 Août 2005 dkim.org  mipassoc.org/mass IETF – Paris 4 Août 2005 dkim.org  mipassoc.org/mass MIPA.
DISPATCH WG: ad hoc meeting on DREGS IETF-76 Mary Barnes (Dispatch WG co-chair) Eric Burger (ad hoc chair) 12 November DREGS ad hoc (DISPATCH) IETF.
DIME WG IETF 82 Dime WG Agenda & Status THURSDAY, November 17, 2011 Jouni Korhonen & Lionel Morand.
DIME WG IETF 84 DIME WG Agenda & Status Tuesday, July 31 st, 2012 Jouni Korhonen, Lionel Morand.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: IETF Liaison Report Date Submitted: March 17, 2011 Presented at IEEE session.
July 2011IETF TRILL WG1 TRILL Working Group TRansparent Interconnection of Lots of Links Mailing list: Tools site:
MPTCP – MULTIPATH TCP Interim meeting #3 20 th October 2011 audio Yoshifumi Nishida Philip Eardley.
CDB Chris Bonatti (IECA, Inc.) Tel: (+1) Proposed PKI4IPSEC Certificate Management Requirements Document IETF #59 – PKI4IPSEC Working.
What makes for a quality RFC? An invited talk to the MPLS WG Adrian Farrel IETF-89 London, March 2014.
21 November 2002IETF 55 - Atlanta, GA, USA1 speechsc Eric Burger Dave Oran Jabber:
TSVWG IETF-68 James Polk Lars Eggert Magnus Westerlund.
TSVWG IETF-76 (Hiroshima) James Polk Gorry Fairhurst With an assist for this meeting from **Magnus Westerlund**
4395bis irireg Tony Hansen, Larry Masinter, Ted Hardie IETF 82, Nov 16, 2011.
November 2010IETF TRILL WG1 TRILL Working Group TRansparent Interconnection of Lots of Links Mailing list: Tools site:
Open Pluggable Edge Services (opes) 61st IETF Meeting Washington, D.C., USA.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: IETF Liaison Report Date Submitted: September 23, 2009 Presented at IEEE session.
NEWTRK WG Paris, August 5, Agenda 0 – agenda bashing – 10m 1 - introduction & status - chair- 10m discussion on the issues with ISD proposal.
Multi6 interim meeting agenda Chairs: Brian Carpenter, Kurt Lindqvist 1.IPR reminder, logistics, agenda bashing 2.Charter review 3.draft-lear-multi6-things-to-think-about-03.txt.
ECRIT Virtual Interim Meeting 3rd June 2009, 1PM EDT (New York) Marc Linsner Hannes Tschofenig.
21 November 2002IETF 55 - Atlanta, GA, USA1 lemonade Eric Burger Glenn Parsons
ROLL Working Group Meeting IETF-81, Quebec City July 2011 Online Agenda and Slides at: bin/wg/wg_proceedings.cgi Co-chairs:
L3VPN WG IETF 78 30/07/ :00-11:30 Chairs: Marshall Eubanks Danny McPherson Ben Niven-Jenkins.
CONEX BoF. Welcome to CONEX! Chairs: –Leslie Daigle –Philip Eardley Scribe Note well.
1 Yet Another Mail Working Group IETF 78 July 29, 2010.
12/13/01RFC Editor Report1 RFC Editor Report Bob Braden for Joyce K Reynolds 52nd IETF Meeting Salt Lake City, Utah December 13, 2001.
IETF Trust Chair Report Ed Juskevicius November 22, 2008 Minneapolis, MN, USA.
IETF Trust Chair Report Ed Juskevicius November 19, 2008 Minneapolis, MN, USA.
SIP working group status IETF#70 Keith Drage, Dean Willis.
Unrestricted Derivative Works Scott Bradner
IETF 831 Chairs: Flemming Andreasen Miguel A. Garcia.
November 20, 2002IETF 55 - Atlanta1 VPIM Voice Profile for Internet Mail Mailing list: To subscribe: send.
Mary Barnes (WG co-chair) Cullen Jennings (WG co-chair) DISPATCH WG IETF 90.
Lemonade IETF 70 Eric Burger Glenn Parsons
MPTCP – MULTIPATH TCP WG meeting #5 Nov 8 th & 10 th 2010 Beijing, ietf-79 Yoshifumi Nishida Philip Eardley.
DMM WG IETF 84 DMM WG Agenda & Status Tuesday, July 31 st, 2012 Jouni Korhonen, Julien Laganier.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: IETF Liaison Report Date Submitted: September 16, 2010 Presented at IEEE session.
1 An RFC Stream for the IRTF Wednesday, 12 March 2008 Scalable Adaptive Multicast RG.
Slide 1 August 2005, Paris, FranceIETF DNSEXT 2929bis etc. Donald E. Eastlake 3 rd
Transport Layer Security (TLS) IETF 73 Thursday, November Chairs: Eric Rescorla Joe Salowey.
MPTCP – MULTIPATH TCP WG meeting Tuesday 23 rd & Friday 26 th March 2010 Anaheim, ietf-77.
ROLL Working Group Meeting IETF-82, Tapei, November 2011 Online Agenda and Slides at: bin/wg/wg_proceedings.cgi Co-chairs:
MODERN BoF Managing, Ordering, Distributing, Exposing, and Registering telephone Numbers IETF 92.
IETF #85 - NETCONF WG session 1 NETCONF WG IETF 85, Atlanta, USA WEDNESDAY, November 7, Bert Wijnen Mehmet Ersue.
NETWORK-BASED MOBILITY EXTENSIONS WG (NETEXT) July 28 th, 2011 IETF81 1.
SALUD WG IETF 78 Maastricht Friday, July 30, London Chair: Dale R. Worley.
DIME WG IETF 83 DIME WG Agenda & Status Thursday, March 29, 2012 Jouni Korhonen, Lionel Morand.
SIPPING Working Group IETF 67 Mary Barnes Gonzalo Camarillo.
Mon 23 Mar 2015SIDR IETF 92 Dallas, TX, US1 SIDR Working Group IETF 92 Dallas, TX, US Monday, 23 Mar 2015.
SNMP (Simple Network Management Protocol) Overview
<draft-bradner-rfc-extracts-00.txt>
ID Tracker States: An Internet Draft’s Path Through the IESG
Lesson 16 Enhancing Documents
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.
SNMP (Simple Network Management Protocol) Overview
[place presentation subject title text here]
September, 2001 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Briefing on IEEE Standards Style Manual]
James Polk Gorry Fairhurst
Presentation transcript:

21 November 2002IETF 55 - Atlanta, GA, USA1 The Internet Standards Process For the SPEECHSC Work Group Eric Burger

21 November 2002IETF 55 - Atlanta, GA, USA2 Internet Documents Internet-Drafts –Working documents (works in progress) –No status of any kind, not archived, deleted after 6 months –Announced and disseminated by IETF Secretariat RFCs –Archival document series of the IETF –Not all RFCs are standards-track –Edited, announced, and disseminated by RFC Editor

21 November 2002IETF 55 - Atlanta, GA, USA3 Internet Drafts Anyone Can Submit an Internet-Draft As an Individual Submission –No One Can Stop You –No One May Care Work Group Submission –Requires WG Chair Approval

21 November 2002IETF 55 - Atlanta, GA, USA4 Individual Draft Life Cycle Submit Draft as an Individual Draft If Group Consensus, Take On As Work Group Item If Not In Charter, Requires Rechartering (AD Approval) Documents May Progress as Individual Drafts

21 November 2002IETF 55 - Atlanta, GA, USA5 Standards Track Submissions Happy Path –Fiction Reality Working group, individual, IESG or IAB Area Directorate Individual IESG RFC Editor

21 November 2002IETF 55 - Atlanta, GA, USA6 Where is my Internet Draft? Draft Tracker – RFC Editor Queue –

21 November 2002IETF 55 - Atlanta, GA, USA7 Standard Levels Proposed Standard –Complete, credible specification –Demonstrated utility –At least 6 months, no longer than 2 years, then either elevated, deprecated, or recycled Draft Standard –Multiple, independent, interoperable implementations –Limited operational experience - works well –At least 4 months, no longer than 2 years, then either elevated, deprecated, recycled, or back to Proposed

21 November 2002IETF 55 - Atlanta, GA, USA8 General Formatting Guide (1/2) 7-bit, Printable ASCII Text –Printable ASCII + CR, LF, FF –Microsoft em-Dash, Smart Quotes, etc. Bad Form! –No Underlining, Overstrike, Bold, etc. –Turn Off AutoCorrect Page Size –72 characters per line –58 lines per page –Form Feed at end of every page

21 November 2002IETF 55 - Atlanta, GA, USA9 General Formatting Guide (2/2) Ragged Right No Hyphenation for Line Breaks No Footnotes Two Spaces Between Sentences Standard Headers and Footers

21 November 2002IETF 55 - Atlanta, GA, USA10 Templates Microsoft Word Template –RFC 3285: Using Microsoft Word to create Internet Drafts and RFCs –ftp://ftp.ietf.org/internet-drafts/2- Word.template.rtfftp://ftp.ietf.org/internet-drafts/2- Word.template.rtf –ftp://ftp.ietf.org/internet-drafts/crlf.exeftp://ftp.ietf.org/internet-drafts/crlf.exe – d/Internet_Draft_Template.dothttp://flyingfox.snowshore.com/i- d/Internet_Draft_Template.dot nroff, LaTeX, XML Options, too

21 November 2002IETF 55 - Atlanta, GA, USA11 Intellectual Property Rights (IPR) READ RFC 2026 OK If Encumbered, But With Many Hoops –Ask Chairs Before Submitting! –Need to File IPR Statement With IETF Executive Director

21 November 2002IETF 55 - Atlanta, GA, USA12 RFC Editorial Policies References to RFC 2119 –MUST, MAY, etc. –Normative Reference to RFC 2119 Abbreviations –Spell Out, Except for Most Obvious Ones TCP, UDP, IP, DNS, HTTP, URL, IETF, OSI –First Time In Text –Introduction –Title

21 November 2002IETF 55 - Atlanta, GA, USA13 Draft Sections Internet Draft Boilerplate List of Author(s) or Editor Abstract Table of Contents [if >15 pages] Introduction Body Text IANA Considerations [if any] Security Considerations Normative References Informative References Contributors [if any] Acknowledgements [if any] Author’s Address IPR Notices Copyright Notice ISOC Acknowledgement

21 November 2002IETF 55 - Atlanta, GA, USA14 Mandatory Statements (Boilerplate) Rights Grant, One Of: –Full Compliance With S. 10 of RFC 2026 Standards Track Publications –No Derivative Works Republishing Other Standards –No Rights Other Than I-D Publication No Plan to Publish Internet-Draft Disclaimer

21 November 2002IETF 55 - Atlanta, GA, USA15 Authors Should Be One Author –Principal Author of Individual Draft –Editor of Work Group Draft –NO MORE THAN 5 ALLOWED Authorship Has Implications –E.g., Authors’ 48-Hour Period Significant Contributors Go In Contributors’ Section

21 November 2002IETF 55 - Atlanta, GA, USA16 Abstract Concise, Yet Comprehensive Typically 5-10 Lines 20 Lines Generally Unacceptable This Is The Advertisement for Draft –Interesting Enough for People Outside Work Group to Want to Read Draft Expand Abbreviations Self-Contained; No References

21 November 2002IETF 55 - Atlanta, GA, USA17 Table of Contents Required if RFC > 30 Pages Recommended if RFC > 15 Pages Reasonable Granularity –Lots of Entries Pointing to Same Page Bad

21 November 2002IETF 55 - Atlanta, GA, USA18 Content Guidelines All User-Visible Text Fields Must Be International-Safe (RFC 2277) All MIBs, ABNF, Pseudo-Code Must Be Correct Internet Addresses Should be FQDN’s and Not Numbers –example.net, example.org, example.com (RFC 2606) – /24 (RFC 3330) –DO NOT USE REAL ADDRESSES

21 November 2002IETF 55 - Atlanta, GA, USA19 Protocol Guidelines IPv6 Is Here; Nothing Should Be IPv4- Only Congestion Safe (RFC 2914) Checksums –Explicitly Specify Fields –Don’t Forget Checksum Itself

21 November 2002IETF 55 - Atlanta, GA, USA20 IANA Considerations (RFC 2434) Create or Modify Namespace –For Authoritative Namespace Mapping –Administered Namespace Specify Guidelines –Expert Review –RFC –FCFS Specify Initial Values

21 November 2002IETF 55 - Atlanta, GA, USA21 Security Considerations Meaningful Exploration of Security Issues –Risks –Solutions –Workarounds Resources –RFC 2401 – Security Architecture –RFC 2316 – Security Background –draft-iab-secmech-01– Guidelines

21 November 2002IETF 55 - Atlanta, GA, USA22 References No URL’s, Unless Only Reference (e.g., W3C) –Add As Much Information As Possible to Aid Finding Document –Reference ID, Title, Author, Date, etc. Two Types, Each in Own Section –Normative (Part of Specification) –Informative (History, Background)

21 November 2002IETF 55 - Atlanta, GA, USA23 Reference Style RFC Style –Endnote in Square Brackets –Reference Style –Van Dyke, J., Burger, E., Spitzer, A., O'Connor, W., "Basic Network Media Services with SIP", draft-burger-sipping-netann- 02.txt, June 2002, work in progress –Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997 –Floyd, S., Daigle, L., "IAB Architectural and Policy Considerations for Open Pluggable Edge Services", RFC3238, January 2002

21 November 2002IETF 55 - Atlanta, GA, USA24 Useful Reading Material RFC 2026 – the process RFC 2223bis (draft-rfc-editor-rfc2223bis) – the document format Guidelines to Authors of Internet-Drafts RFC 2360 – doing it right RFC 1958 – what’s known to be good and bad RFC 2360 – MUST Reading for Success

21 November 2002IETF 55 - Atlanta, GA, USA25 Useful URLS IETF Home Pagewww.ietf.orgwww.ietf.org The Tao of the IETF Novice’s Guidewww.imc.org/novice- ietf.htmlwww.imc.org/novice- ietf.html Internet-Draft Nitswww.ietf.org/ID- nits.htmlwww.ietf.org/ID- nits.html

21 November 2002IETF 55 - Atlanta, GA, USA26 Parting Thoughts Don’t Despair! Time From –00 To RFC: 23 Months Time On RFC Editor Queue –Median 9 Weeks –Long-Tail Distribution: Up To 2 Years You Do Get Your Name In Lights, If You Persevere