Re: [Internetgovtech] Contracts, what problems we are solving (Was: Re: Transition to the web)

S Moonesamy <sm+ietf@elandsys.com> Tue, 15 July 2014 17:38 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: internetgovtech@ietfa.amsl.com
Delivered-To: internetgovtech@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B6B11A0AC0 for <internetgovtech@ietfa.amsl.com>; Tue, 15 Jul 2014 10:38:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.441
X-Spam-Level:
X-Spam-Status: No, score=-2.441 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.651, T_DKIM_INVALID=0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B-WrsKgTL5y1 for <internetgovtech@ietfa.amsl.com>; Tue, 15 Jul 2014 10:38:56 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 869A71A0AAC for <internetgovtech@iab.org>; Tue, 15 Jul 2014 10:38:56 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.145.218]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s6FHcfgM007469 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 15 Jul 2014 10:38:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1405445933; x=1405532333; bh=EHr376US3F5mBfdPKU1I8uGjHz7fQAgHQCLz2B2Y8vM=; h=Date:To:From:Subject:In-Reply-To:References; b=mCZsyoMZJgZjWEUaLGYg1DjpjJxgO6xz15e2nB2xy/e6NkKd0exjbC5WN5dTDAB6l wme7ee0ORgG0Gtwwdr8rSgFnFHChXSlvr4zlMrahkUHxXgx+0nOzkO/lBMUMwGthoy bf9kqpaAv0SzN7MhwMaSPiNT7WPgBNy0ew3XFKPM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1405445933; x=1405532333; i=@elandsys.com; bh=EHr376US3F5mBfdPKU1I8uGjHz7fQAgHQCLz2B2Y8vM=; h=Date:To:From:Subject:In-Reply-To:References; b=J+rJgos9U2aZ7M3I3S8Z2KWdVOuhINHhx8QeeiS7uvV6vsP5ikK0rBKo1hWWY9rNc 1kppobDOxaKy7mKmnv80BQ7ocaHd8qq6vIZRYLr6/EE+G1h3W2mi5mAmRYc10yyV1T 0WWpMw/xQqxdp3lomwrwhoaFylWZj/X4HzBp30gQ=
Message-Id: <6.2.5.6.2.20140715100237.08757120@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 15 Jul 2014 10:31:19 -0700
To: Andrew Sullivan <ajs@anvilwalrusden.com>, internetgovtech@iab.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <20140715142048.GE8847@mx1.yitter.info>
References: <53C06E7C.4010903@gmail.com> <CAD_dc6ihUvV8SDkmoc3fGHWoOoR6nFhRz-=tgCjKnuNvRO2JXw@mail.gmail.com> <53C0F1D9.3090400@cisco.com> <53C17B5C.4090600@abenaki.wabanaki.net> <C5750A628D4D973F3C44F6DC@JcK-HP8200.jck.com> <53C1B2C6.40501@meetinghouse.net> <72F8472D-2913-4BEC-9260-6DAC7791BBF8@virtualized.org> <53C1DD6C.8030501@gmail.com> <43DD1894-54A8-44D0-AE58-6F3D395F43DD@ericsson.com> <53C4000C.4030401@dcrocker.net> <20140715142048.GE8847@mx1.yitter.info>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: http://mailarchive.ietf.org/arch/msg/internetgovtech/NK2A-ud0KTUCZ6jCrdTqLSjV4rs
Subject: Re: [Internetgovtech] Contracts, what problems we are solving (Was: Re: Transition to the web)
X-BeenThere: internetgovtech@iab.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Internet Governance and IETF technical work <internetgovtech.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/internetgovtech>, <mailto:internetgovtech-request@iab.org?subject=unsubscribe>
List-Archive: <http://www.iab.org/mail-archive/web/internetgovtech/>
List-Post: <mailto:internetgovtech@iab.org>
List-Help: <mailto:internetgovtech-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/internetgovtech>, <mailto:internetgovtech-request@iab.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jul 2014 17:38:57 -0000

Hi Andrew,
At 07:20 15-07-2014, Andrew Sullivan wrote:
>I think the possibility that the IETF could change the provider for
>the protocol parameters registry is pretty high, but the way we might
>pay for that change is perhaps unclear.  That is, it's nice of ICANN
>to provide us this service for free right now, and it's also really
>great that they do a good, satisfying job.  If that should cease to be
>the case, of course, the IAB could inform ICANN that we were making a
>change, and then we could just start publishing the data on a
>different set of web pages published somewhere else.  Since the IETF
>is the change control authority for the data in the IANA registries,
>there isn't (nominally) anyone else who could disagree with that
>conclusion.  This has been the IETF and IAB position all along, and at
>the igovupdate BoF in London we heard the Chair of the ICANN Board say
>quite the same thing.  So, I don't think there's any real issue there.

There are eleven other groups represented in the discussions.  The 
ICANN Board is not part of those groups.  If there isn't anyone who 
would disagree with that conclusion it may help if that position 
could be expressed publicly.  The IETF could then have its (internal) 
discussion about the questions in your message and the other messages 
posted to this mailing list.

Regards,
S. Moonesamy