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

S Moonesamy <sm+ietf@elandsys.com> Tue, 15 July 2014 19:10 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 452341B2904 for <internetgovtech@ietfa.amsl.com>; Tue, 15 Jul 2014 12:10:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level:
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651] 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 4v5deVQz0BMT for <internetgovtech@ietfa.amsl.com>; Tue, 15 Jul 2014 12:10:16 -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 54DAD1B2902 for <internetgovtech@iab.org>; Tue, 15 Jul 2014 12:10:16 -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 s6FJA21e001680 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 15 Jul 2014 12:10:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1405451415; x=1405537815; bh=V4L/Gretb7Q6KKoEjKuRqqDHPDF2J1KoZ1htC6xgbls=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=YOIUiUjtiIzdoYfA93Z4PSX3r0vCPTNk7JClbnYK73QJR16v0j/z9j49rtde42KhU HgsdsDYxu3nCsfLS7Nx0kEU/rw4CRNwHiFYy1ow8Rld85Jtrm54o951w2fJpUojD46 5a3vktbZTVKz6dZBmtndljcGNB9fwaSf8k40lVTk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1405451415; x=1405537815; i=@elandsys.com; bh=V4L/Gretb7Q6KKoEjKuRqqDHPDF2J1KoZ1htC6xgbls=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=EmvdQamvS/VA0OUusIo6UBgd49Z8aKRSBe4M6ir3ytpm05ezUDSmewRZqlOY+frE3 90+cII/4djxDAPGdshDPVGK4Myapph6L9FeP5qGq6f/b2v8wvTO442xLgSdCPuxWh2 AsGTqULmaFcFA/mGOVBkKeaNZwe9/gTMyCdwtBpM=
Message-Id: <6.2.5.6.2.20140715110728.08a97a98@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 15 Jul 2014 12:09:27 -0700
To: David Conrad <drc@virtualized.org>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <133C8BA9-EEC5-48A2-941D-61E9E6371BD3@virtualized.org>
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> <6.2.5.6.2.20140715100237.08757120@resistor.net> <133C8BA9-EEC5-48A2-941D-61E9E6371BD3@virtualized.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: http://mailarchive.ietf.org/arch/msg/internetgovtech/2xL-gCGu_ZfESbVdMeq0N2zm99k
Cc: internetgovtech@iab.org
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 19:10:19 -0000

Hi David,
At 11:01 15-07-2014, David Conrad wrote:
>Given the various references (some hardwired?) to IANA.ORG, that 
>might get a bit confusing. Perhaps it might be important to ensure 
>that there be a clear understanding that the IANA.ORG domain name is 
>'owned' by the IAB/IETF and/or associated with the protocol 
>parameters function?

I have been thinking about the domain name.  I think that IANA.ORG is 
not an IETF asset.  The association of the protocol parameters 
function with the domain name could be a headache.  My guess would be 
not to deal with that now.

>Well, the position was expressed publicly (it's in the transcript of 
>the igovupdate session).  Perhaps you mean expressed formally in writing?

I'll explain that in my response to Dr Crocker instead of here to 
keep that in one message.

Regards,
S. Moonesamy