November 8, 2005"Field of Use" RFC Modification1 “Field of Use” RFC Modification Permissions David L. Black EMC Corporation November 8, 2005.

Slides:



Advertisements
Similar presentations
© 2006 Open Grid Forum Grid Resource Allocation Agreement Protocol GRAAP-WG working session 2 Wenesday, 17 September, 2008 Singapore.
Advertisements

1 of 2 This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. © 2007 Microsoft Corporation.
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.
CPIT 102 CPIT 102 CHAPTER 1 COLLABORATING on DOCUMENTS.
1 Improved DNS Server Selection for Multi-Homed Nodes draft-savolainen-mif-dns-server-selection-04 Teemu Savolainen (Nokia) Jun-ya Kato (NTT) MIF WG meeting.
1 of 3 This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. © 2007 Microsoft Corporation.
Implementing Application Protocols. Overview An application protocol facilitates communication between applications. For example, an client uses.
Word Templates- Documents Directly from GP.
Early Media in SIP: Problem Statement, Requirements, and Analysis of Solutions draft-barnes-sip-em-ps-req-sol Richard Barnes BBN Technologies IETF 68,
L2VPN WG “NVO3” Meeting IETF 82 Taipei, Taiwan. Agenda Administrivia Framing Today’s Discussions (5 minutes) Cloud Networking: Framework and VPN Applicability.
PPSP Working Group IETF-89 London, UK 16:10-18:40, Tuesday, Webex: participation.html.
Tcpsecure ipr 1 Cisco IPR Disclosure Relating to tcpsecure Scott Bradner
This chapter is extracted from Sommerville’s slides. Text book chapter
CCAMP Working Group Online Agenda and Slides at: Tools start page:
1st NRC Meeting, October 2006, Amsterdam 1 ICCS 2009 Field Operations.
Framework for Performance Metric Development draft-morton-perf-metrics-framework-01.txt Alan Clark IETF 70 PMOL WG.
Brett Neely IP Next Generation. To boldly go where no network has gone before...
IEEE MEDIA INDEPENDENT HANDOVER DCN: REVP m-session-64-closing-report Title: m Session #64 Closing Report Date Submitted:
IPR in the IETF Personal Thoughts from an AD Adrian Farrel Thanks to: Dave Ward, Ross Callon, Scott Brander, Jorge Contreras,
DIME WG IETF 82 Dime WG Agenda & Status THURSDAY, November 17, 2011 Jouni Korhonen & Lionel Morand.
MPTCP – MULTIPATH TCP Interim meeting #3 20 th October 2011 audio Yoshifumi Nishida Philip Eardley.
68th IETF – OPS area – XML MIB Modules XML MIB Modules draft-stephan-ops-xml-mib-module-template-00 draft-stephan-ops-xml-mib-module-template-00.
XCON IETF 64 November 8 th – 9 th, 2005 Vancouver, BC, Canada.
IETF #82 DRINKS WG Meeting Taipei, Taiwan Fri, Nov 18 th
21 November 2002IETF 55 - Atlanta, GA, USA1 speechsc Eric Burger Dave Oran Jabber:
© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.
November 2010IETF TRILL WG1 TRILL Working Group TRansparent Interconnection of Lots of Links Mailing list: Tools site:
IETF #81 DRINKS WG Meeting Québec City, QC, Canada Tue, July 26 th, 2011.
Multi6 Working Group IETF-61, Washington D.C November 8-12, 2004.
Draft-elwell-sipping- redirection-reason-00 Author: John Elwell
NEWTRK WG Paris, August 5, Agenda 0 – agenda bashing – 10m 1 - introduction & status - chair- 10m discussion on the issues with ISD proposal.
IETF/JTC1 Agreement on IS-IS protocol development
Models to manage G parameters draft-galikunze-ccamp-g snmp-mib-11.txt Gabriele Galimberti Cisco Systems Ruediger KunzeDeutsche Telekom Lam,
ECRIT Virtual Interim Meeting 3rd June 2009, 1PM EDT (New York) Marc Linsner Hannes Tschofenig.
1 Virtual Router Redundancy Protocol (VRRP) San Francisco IETF VRRP Working Group March 2003 San Francisco IETF Mukesh Gupta / Nokia Chair.
SIP working group IETF#70 Essential corrections Keith Drage.
1 VCID Notification over ATM Link N. SonyCSL K. Toshiba L. Ericsson Ennovate Networks H. Toshiba G.Swallow.
Configuration Management CSCI 5801: Software Engineering.
1 CA203 Presentation Application Reviewing and Sharing a Presentation Lecture # 11.
Draft-huston-sidr-rfc6490-bis Geoff Huston Slide 1/6.
File: /ram/wgchairs.sxi Date: 7 January, 2016 Slide 1 Process and Tools (PROTO) Team General Area Meeting IETF59, Seoul, Korea -- March 2004
xxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxx Title: IETF Liaison Report Date Submitted: November 16, 2006 Presented.
1 Chapter 12 Configuration management This chapter is extracted from Sommerville’s slides. Text book chapter 29 1.
Unrestricted Derivative Works Scott Bradner
Wed 24 Mar 2010SIDR IETF 77 Anaheim, CA1 SIDR Working Group IETF 77 Anaheim, CA Wednesday, Mar 24, 2010.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Liaison Report – Work Related to Date Submitted:
Derivative Works Authors Rights in RFCs authors retain almost all copy rights in the material in their RFCs IETF/ISOC gets rights needed.
1 IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: IEs related Issues Date Submitted: March 2007 Presented at IEEE session.
A RTCP-based Retransmission Protocol for Unicast RTP Streaming Multimedia draft-podolsky-avt-rtprx-00.txt Matthew Podolsky, Koichi Yano, and Steven McCanne.
© 2006 Open Grid Forum Network Services Interface OGF 33, Lyon Guy Roberts, Inder Monga, Tomohiro Kudoh 19 th Sept 2011.
CLUE WG chair: Mary Barnes RTCWEB WG chair: Ted Hardie CLUE & RTCWEB WGs Adhoc Common (SDP/RTP) building blocks IETF-82.
RTP Usage for CLUE draft-lennox-clue-rtp-usage-02 Clue WG, IETF 83, 27 March 2012 Jonathan Lennox Allyn Romanow
IPR WG IETF 62 Minneapolis. IPR WG: Administrivia Blue sheets Scribes Use the microphones Note Well.
ROLL Working Group Meeting IETF-82, Tapei, November 2011 Online Agenda and Slides at: bin/wg/wg_proceedings.cgi Co-chairs:
CSI WG / IETF741/12 Implementation of SeND/CGA and Extensions Beijing University of Posts and Telecommunications HUAWEI.
MODERN BoF Managing, Ordering, Distributing, Exposing, and Registering telephone Numbers IETF 92.
1 Yet Another Mail Working Group IETF 76 November 11, 2009.
Interface to Network Security Functions (I2NSF) Chairs: Linda Dunbar Adrian Farrel IETF 95, Thursday April 7, 2016,
CCAMP Working Group Online Agenda and Slides at: Data tracker:
<draft-bradner-rfc-extracts-00.txt>
Getting Started with CSS
Participants, Patents, and Duty to Inform
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.
pre8prob BOF Background
IKEv2 Mobility and Multihoming Protocol (MOBIKE)
Welcome to the rebuild slide master
ECN Experimentation draft-black-ecn-experimentation
Integrating Office 2013 Programs
Web-based Imaging Management System Working Group - WIMS
YANG Instance Data for Documenting Server Capabilities
Presentation transcript:

November 8, 2005"Field of Use" RFC Modification1 “Field of Use” RFC Modification Permissions David L. Black EMC Corporation November 8, 2005

"Field of Use" RFC Modification2 Problem: RFC text changes Want to change RFC text to support its implementation (draft-josefsson, Sec. 2): 1.Source code comments 2.Table re-formatting for implementation 3.Non-functional ASN.1 edits (e.g., for tool compatibility) 4.Non-functional source/header edits (e.g., for compiler compatibility) 5.Extract/reformat text for online help and manuals All of these involve interoperable implementation of the original RFC !!

November 8, 2005"Field of Use" RFC Modification3 Proposed “Field of Use” Solution Allow anyone to change the text of an RFC in support of implementation of the original RFC –No notice to or permission from the IETF would be required –Does not permit use of changed RFC text for incompatible implementations (will come back to this) Legalese components –Within the “field of use” of implementation of the original RFC, –Anyone is allowed to make, distribute, etc. a “derived work” All 5 examples on previous slide are allowed –Including ASN.1 changes when protocol is not affected

November 8, 2005"Field of Use" RFC Modification4 Changing the Protocol Changing the protocol is outside the “field of use” of implementation of the original RFC. Solution: “Send Draft !!” (Open Issue) –Document the changes in an Internet-Draft. It’s ok to use any RFC text in an Internet-Draft. –The “field of use” permissions apply to that draft All 5 text modification examples on slide 2 are now allowed Note: Based on the Internet-Draft, not the original RFC Distribution of the original RFC and the Internet- Draft are (and remain) unlimited

November 8, 2005"Field of Use" RFC Modification5 New Examples Simon’s , Monday, November 7 1 – Open source protocol modifications –Send Draft - see previous slide. (Open Issue) 2 – Educational usage –Could add education to “field of use” for modification when subject of education is the unmodified protocol –Would forbid assigning a class project to implement an incompatibly modified RFC. Can still write a separate document to specify changes –That document could even be an Internet-Draft Distribution of the original RFC remains unlimited.

November 8, 2005"Field of Use" RFC Modification6 Next Steps Decide whether “field of use” is the WG’s preferred approach –And what the resulting permissions should be If so, assign a small team (including Jorge?) to write the precise legal text. –I am not a lawyer...