Road-map

From IUCG - Internet Users Contributing Group

Jump to: navigation, search

IDNA2008 means that there is nothing to deploy on the Internet side in order to deploy IDNA: by its very nature it is already deployed.

.

Contents


IDNA2010

The issue now is about what we call IDNA2010, i.e. IDNs on the user side (or IDNUS). There are two possible readings of the Internet prior to considering it:

  • the IETF reading, which starts with the IDNA architecture and should continue with John Klensin's IAB RFC on IDNA. Like RFC 5895, it can only propose IETF "SHOULD"s.
  • an Internet Use reading that is in tune with IDNA2008 unleashed concepts. As a result, there can be architectural propositions a plenty, documented by different SDOs, user groups, consortiums, manufacturers, etc. They will propose "MUST"s that must not conflict with IETF "MUST"s as they will perceive them untouchable Internet "ARE"s


Emerging IUse community

Inteplus, ML-DNS, IUI, Netix, etc. are concepts that the emerging IUse community wants to explore as its technical contribution in that area. It was described as research by the IESG, which advocated BoF to discuss them. It will be experimented as such under an "intertest" charter documenting the constraints to respect when using the Internet as its own test-bed (cf. ICANN ICP-3 recommendations) using eTLDs (experimental TLDs) in at least three areas in order to comply with the Internet standard process rules.


Contribution channel

Initially, this public domain IUsers and multiproject exploration was to be directly contributed through the IUCG (Internet Users Contributing Group, iucg@ietf.org) - cf. its charter that as been discussed with the IESG and IAB Chairs. However, the IAB/IESG responses to my preliminary precautionary appeal have shown that this scheme was not appropriate because what we call the IUI (Intelligent/Internet Use Interface) area is not considered a part of the IETF core scope. As such, an IETF public domain stream for the IUCG was, therefore, out of the immediate picture.

The retained solution is, therefore, to proceed in two steps through different initiatives and experimental developments, in turn contributing to a public domain "Architecture Libre/Free Architecture" (ALFA) model that the IUCG will be able to adapt for information to the IETF I_D format. It also includes the organization, assistance, and promotion of the emergence of the IUse/IUsers (structures and users) community structures.


Deployment strategy

The intended deployment plan is as follows:

  • name the IUI architecture and community components for coherent stable referencing (done)
  • deploy their initial websites for their autonomous documentation (mostly done)
  • complete a ML-DNS prototype, individual and collective source.forge (current)
  • document an "intertest" I_D and start gathering intertesters to form an IUse community first ring
  • promote an "IUse" label and industry/lead-user IUI product common image, with a special attention to facilitation
  • hold the first IUser community meeting (spring 2011).
Personal tools