Difference between revisions of "History"

From IUWG
Jump to: navigation, search
(IETF Transition)
(IETF Transition)
Line 25: Line 25:
  
 
The Members of the IUWG therefore decided that their WG could not accept "the IETF Note Well" terms, imposing on them the BCP 78 licence.
 
The Members of the IUWG therefore decided that their WG could not accept "the IETF Note Well" terms, imposing on them the BCP 78 licence.
 +
 +
When the WG/IANAPLAN Draft was approved by the IESG for publication as an RFC, JFC Morfin appealed the IESG: [http://www.ietf.org/iesg/appeal/morfin-2015-03-11.pdf Appeal to the IESG concerning its approval of the "draft-ietf-ianaplan-icg-response" (PDF file) (JFC Morfin; 2015-03-11)].
  
 
== Consequences for the IUWG ==
 
== Consequences for the IUWG ==

Revision as of 16:47, 26 March 2015

The creation of this WG was not intended. It comes as a side effect of the IETF/WG/IANAPLAN.

Due to the calendar that was adopted by this WG/IANAPLAN, a memo could not be submitted as an IETF Draft to be plainly discussed prior to the end of a WGLC and of a key meeting, as specified by the WG Charter, while it was a pragmatic proposal of compromise by an IUsers Libre community regarding the transition of the DNS key functions.

It was therefore, to be published as an independent public domain contribution, discussed and possibly submitted as an IETF Draft at the end of the cut-off time which prevented its planned initial submission. The Libre IUser group created this site for that purpose.

IETF Transition

The {http://www.ietf.org/blog/2015/01/taking-a-step-towards-iana-transition/ announcement] made clear that the IETF ultimate referent is not the IAB anymore but the NTIA:

Quote:

"Our work is not yet complete. There are a number of steps still in front of us. They include the following:
  • Both the numbers and names communities need to complete their proposals. We at the IETF will continue engage with them with their work, just as they assisted us with ours.
  • Later, the IANA Transition Coordination Group (ICG) will assemble a complete proposal and gather community feedback on the result. When ready, they will submit the final proposal to the NTIA.
* The NTIA must then consider and approve the proposal.
* Finally it must be implemented.
While there will assuredly be some bumps along the road to success, the IETF leadership are committed to ensuring a good outcome for the Internet.
Jari Arkko, IETF Chair and Eliot Lear, IAB

/Quote.

The Members of the IUWG therefore decided that their WG could not accept "the IETF Note Well" terms, imposing on them the BCP 78 licence.

When the WG/IANAPLAN Draft was approved by the IESG for publication as an RFC, JFC Morfin appealed the IESG: Appeal to the IESG concerning its approval of the "draft-ietf-ianaplan-icg-response" (PDF file) (JFC Morfin; 2015-03-11).

Consequences for the IUWG

As a result:

  • the IUWG Free/Libre Working Group could only stay independent from the new IETF RFC 6852 type of Global Community; and initiate relations with the Catenet Scic RFC 6852 Global Communities. It is understood that Catenet Scic will endorse the OpenStand principles.
  • Any contribution made within the IUWG framework is considered an "IUWG Contribution". Such contributions include oral statements, as well as written and electronic communications made at any time or place, which are addressed to:
  • The IUWG and Catenet Scic meetings and assemblie
  • Any IUWG or Catenet Scic mailing list, including the IUWG and Catenet Scic lists themselves, any working group or design team list, or any other list functioning under IUWG and/or Catenet Sic auspices
  • Any IUTF and Catenet Scic working group or portion thereof
  • Any Birds of a Feather (BOF) session
All IUWG Contributions are subject to a CC BY SA licence.
Care will be taken that only duely registered members can post on IUWG and Catenet Scic mailing lists in order to protect their IPRs established under more restrictive frameworks.