Return-Path: X-Original-To: regext@ietfa.amsl.com Delivered-To: regext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DD1B120147 for ; Wed, 6 Nov 2019 14:48:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=secureservernet.onmicrosoft.com 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 719My71rzPyO for ; Wed, 6 Nov 2019 14:48:43 -0800 (PST) Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-eopbgr750130.outbound.protection.outlook.com [40.107.75.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA6EA1200B1 for ; Wed, 6 Nov 2019 14:48:42 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=JyqOK+3qV7n53nCsawfS6BZ6a/mGEqIX/A8GOcd0k4b+71O9veSLeBDGuixDdNA0mPnuZpNRcEeacYcMqK6u88rf+qZ7J/qigA3dy/YVfyl8SxWJw720sCBdS8gxPI5GGehQPUbAVnMONXxesQrIaWG1Ze/JxBuAFEzokFxGftBG493oEM5iP+7JQn4f3Rsc8oEyjIKxGXtESxvarFeovlrOYL42cCTghmB0N5ryuxzuO5EB1dauopJ9/yaqWbdO89gYZY4i+T09ICU2IRSYazdokdCooH+Icf6oUqjb47sMTqdVcBm30OIAo2s1r+Vu+YlhIUcccZqMt2pCnd+wVA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=otnQsi8U4kJGK4TcJPUNgajNENKfXbEjlnynpjRuuPE=; b=iH80LlQMrqUa0D4tuyO2CoebbrbdgTZ2M5B+ozsBW6ZPcvpTK6/bK/4tDydbyHnsdbyd854iHU0b+ONMsG1a1/Kvbm7bwIm7mKETxouacSDc3mItdt7M10pVDnhK496VAlol90VpcNy1AreGumQgKQJFeEYo6czziuLgLNIe+McrlMJSGpYPYqLTxqPQCbNlZ5XBSkteHr481DtiNK5FAZnTwAzytlw9WehY6VF05fHRhcZNPYFC9NRu8Zq98jEP26PLE5KEhsennrh9Wll0MRjw/+5kZseTtYp+bDCaTjPjZOtDp5A8rluZe1HthKT/S5rsAWDSjdSGGvnmvlmGYg== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=godaddy.com; dmarc=pass action=none header.from=godaddy.com; dkim=pass header.d=godaddy.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=secureservernet.onmicrosoft.com; s=selector1-secureservernet-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=otnQsi8U4kJGK4TcJPUNgajNENKfXbEjlnynpjRuuPE=; b=iKc9K5I/EKEhwnuRP7uCNusCSebPac41C5/+haP058OMWxg9HR4cKOdNhasCBUIjffFO3vkCNLGsd+QiIK7fF3zbLJ+8aR71YZtgmjBvtsr714wbh9TwfDWHZIBBiOVIE7zyuo9ASZEC0e1X6716VAyt7lm193mGj1YJadWJ+/k= Received: from BL0PR02MB5491.namprd02.prod.outlook.com (20.177.207.214) by BL0PR02MB4707.namprd02.prod.outlook.com (52.132.14.205) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2408.24; Wed, 6 Nov 2019 22:48:40 +0000 Received: from BL0PR02MB5491.namprd02.prod.outlook.com ([fe80::796f:fb89:fee5:f735]) by BL0PR02MB5491.namprd02.prod.outlook.com ([fe80::796f:fb89:fee5:f735%5]) with mapi id 15.20.2408.024; Wed, 6 Nov 2019 22:48:40 +0000 From: Roger D Carney To: "regext@ietf.org" Thread-Topic: Registry-Registrar Reporting Thread-Index: AdWShh9Xt498K1q5RNyjWd9WEjCQYw== Date: Wed, 6 Nov 2019 22:48:40 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rcarney@godaddy.com; x-originating-ip: [66.171.166.114] x-ms-publictraffictype: Email x-ms-office365-filtering-ht: Tenant x-ms-office365-filtering-correlation-id: f81078f7-3c8e-4d73-6b57-08d7630b7807 x-ms-traffictypediagnostic: BL0PR02MB4707: x-ms-exchange-purlcount: 9 x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:10000; x-forefront-prvs: 02135EB356 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(366004)(346002)(136003)(39860400002)(376002)(396003)(189003)(199004)(66066001)(186003)(66446008)(66946007)(606006)(2501003)(478600001)(1730700003)(74316002)(5660300002)(99286004)(316002)(25786009)(7736002)(476003)(66476007)(7696005)(81156014)(66574012)(81166006)(9686003)(71190400001)(6306002)(6436002)(790700001)(236005)(52536014)(54896002)(71200400001)(86362001)(14454004)(55016002)(8676002)(6916009)(6116002)(486006)(6506007)(102836004)(2351001)(2906002)(561944003)(256004)(5640700003)(64756008)(26005)(76116006)(33656002)(8936002)(3846002)(66556008)(3480700005); DIR:OUT; SFP:1102; SCL:1; SRVR:BL0PR02MB4707; H:BL0PR02MB5491.namprd02.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: godaddy.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: SM5USzYBDFhi+eLtE9Bq15KHAz4vBY2VFS1UrlFd42yFjUL+3NnORvECzCPFFFAeLYBXzyT+VlQCMG1m25b4ROk4yXwP9qr9Ftik2vItR9vWnlSHiU62+925SA5sh5HLjwCZpSGb9UWS98URd3zwzbuXNW2QU3v6edvlG3Ak9UOW3CKUNftFvjrpzd4WbvXIlmgrxtKKKpAPrIFmrDN4mvq1JoaGR4hF2JR3g+3WWogKp/LBRIbux26cdHHoZ3wQCMIL9fjkipuJu8KuGjrf9pZn+DWJ/NRCCDam4Tco/d5piYddET4SFpeUoDWLSeGJ6gL0U6JZVbk84QNjAcaDAZmb6V2BNN/4H0FWeQ1ady/77/enfAX7Gy0pFZ3YYwGqXwpQOGPW4N/LPGREPyGk5UtL0v97S4XoR7Zf0ANoMy9p1BfRT79Ke8ttmUw1ix+Up6apKH4bmNErOhLw2wS3b7tMfa4aholEHbNrN1Qh5ic= x-ms-exchange-transport-forked: True Content-Type: multipart/alternative; boundary="_000_BL0PR02MB5491A7F4EB7EEA75CD05F245B1790BL0PR02MB5491namp_" MIME-Version: 1.0 X-OriginatorOrg: godaddy.com X-MS-Exchange-CrossTenant-Network-Message-Id: f81078f7-3c8e-4d73-6b57-08d7630b7807 X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Nov 2019 22:48:40.2168 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: d5f1622b-14a3-45a6-b069-003f8dc4851f X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: oG8JX0k7bwIWHFnmLrFjetE+2P/Ek0pr7gAZH4jXdR6wc1N3WiAQW58YzQm1idh5WHQP4WipzdvCSpLIz/9ZkQ== X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL0PR02MB4707 Archived-At: Subject: [regext] Registry-Registrar Reporting X-BeenThere: regext@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Registration Protocols Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Nov 2019 22:48:47 -0000 --_000_BL0PR02MB5491A7F4EB7EEA75CD05F245B1790BL0PR02MB5491namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Good Afternoon, I took an action item out of the Interim REGEXT Meeting held 03NOV2019 in r= egards to the Registry-Registrar Reporting discussion. We discussed, for almost two hours, several proposals around standardizing = Registry-Registrar Reports. Roughly there were three proposals: * Column/Report Registry - Create two (2) first come first serve regi= stries at IANA to contain the industry agreed standardized 1) column names = and definitions and 2) Report Name and column mappings. This was a new prop= osal presented at the Interim Meeting. * Best Practice - Define each standard report as an RFC. Over the pas= t year or so there have been several drafts created to document proposed re= porting standards between Registries and Registrars. (draft-mcpherson-satt= ler-report-structure, draft-mcpherson-sattler-reporting-repository, d= raft-mcpherson-sattler-transaction-report, draft-sattler-premium-domain-= fee-report, draft-sattler-domain-inventory-report, draft-sattler-domain-drop-= list-report, draft-sattler-unavailable-domain-report, draft-sattler-contact-= inventory-report). * Dataset File Format - A proposed format that can be used to define = and pass bulk data between Registry-Registrar. There was some discussion on= possible modifications that would possibly allow report definition and del= ivery (draft-gould-regext-dataset). To provide focus and eliminate as much duplicate effort as possible, I woul= d propose that the WG proceed with the Column/Report Registry concept; remo= ve (from the REGEXT backlog) the internet drafts created under the Best Pra= ctice concept; and continue with the Dataset File Format for bulk operation= s but not be used/modified for these standard reports. For discussion details please see the meeting notes (coming soon). Thanks Roger --_000_BL0PR02MB5491A7F4EB7EEA75CD05F245B1790BL0PR02MB5491namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Good Afternoon,

 

I took an action it= em out of the Interim REGEXT Meeting held 03NOV2019 in regards to the Regis= try-Registrar Reporting discussion.

 

We discussed, for a= lmost two hours, several proposals around standardizing Registry-Registrar = Reports. Roughly there were three proposals:

·       Column/Repo= rt Registry – Create two (2) first come first serve registries at IAN= A to contain the industry agreed standardized 1) column names and definitio= ns and 2) Report Name and column mappings. This was a new proposal presented at the Interim Meeting.

·       Best Practi= ce – Define each standard report as an RFC. Over the past year or so = there have been several drafts created to document proposed reporting stand= ards between Registries and Registrars.  (draft-mcpherson-sattler-report-structure, draft-mcpherson-sattler-reporting-repository, draft-mcpherson-sattler-transaction-report, draft-sattler-premium-domain-fee-report, draft-sattler-domain-inventory-report, draft-sattler-domain-drop-list-report, draft-sattler-unavailable-domain-report,  draft-sattler-= contact-inventory-report).

·       Dataset Fil= e Format – A proposed format that can be used to define and pass bulk= data between Registry-Registrar. There was some discussion on possible mod= ifications that would possibly allow report definition and delivery (draft-gould-regext-dataset).

 

To provide focus an= d eliminate as much duplicate effort as possible, I would propose that the = WG proceed with the Column/Report Registry concept; remove (from the REGEXT= backlog) the internet drafts created under the Best Practice concept; and continue with the Dataset File Format= for bulk operations but not be used/modified for these standard reports.

 

For discussion deta= ils please see the meeting notes (coming soon).

 

 

Thanks

Roger

 

--_000_BL0PR02MB5491A7F4EB7EEA75CD05F245B1790BL0PR02MB5491namp_--