IETF Logo Mail Archive

Re: [eppext] I-D Action: draft-lozano-ietf-eppext-registrar-expiration-date-00.txt

"Gould, James" <JGould@verisign.com> Thu, 21 January 2016 20:08 UTC

Return-Path: <JGould@verisign.com>
X-Original-To: eppext@ietfa.amsl.com
Delivered-To: eppext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9513D1A90B1 for <eppext@ietfa.amsl.com>; Thu, 21 Jan 2016 12:08:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001] 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 aLidxraeLzgj for <eppext@ietfa.amsl.com>; Thu, 21 Jan 2016 12:08:09 -0800 (PST)
Received: from mail-oi0-x262.google.com (mail-oi0-x262.google.com [IPv6:2607:f8b0:4003:c06::262]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8A211A90AD for <eppext@ietf.org>; Thu, 21 Jan 2016 12:08:08 -0800 (PST)
Received: by mail-oi0-x262.google.com with SMTP id x140so3062336oif.3 for <eppext@ietf.org>; Thu, 21 Jan 2016 12:08:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verisign-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :content-type:mime-version; bh=6qcjBlIYlNAvlOWpajUME+4zacxybEPFoVyJad1Atq8=; b=Hf/gXUIrk3DbpQZRPM58vn3ViV8kjrH8QCiQGxekG8ry0dRdKY3SaMgK8rXGpj1FjM xfmOJuhIUSbpEu8Q+ylqqKBcxU7a3pmeu3adH4TcUjQtae7M66Du3DkBWUnlPVKMOj1r Wv4EA+N4NX1/ZmtBz8CDYa3JotePQoYtrovyocxwW2ZARe/OveQv+Q/KQoI9AY9yyMCw nv/H/5JJ4CCIESqiItWRQ1JHzGgeN8hegdnHsrQFCbvvuHnK80WldU6f1oPx0yoineEO BSuFwxkXg+ocqJhmF4/FK2MfGb2PCMIZLIKNX/hA479RmQ7pJIMiJfHN9NfY81g9WkKV jkow==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:content-type:mime-version; bh=6qcjBlIYlNAvlOWpajUME+4zacxybEPFoVyJad1Atq8=; b=TbiZUom8+ZtvS1Zq1V5Y5JpPEAocVyKZP59YiiuIrEhBR/JlqqEVknExfm+J9HtE1C L1RdLPufB/PO+ubZNoZsc02UbJ16mLhfmj7JLb66cPOWxaRR1JxtYBOS3zfVADg6vcvp hrfKdNRMnI/W9710gfIHIHDeYg5FET+sQCtnrgQC1ggevqGFcflSMwLU3MQZ0TR5APmF dLu1vxW/ySfZqBTkcQcKcLvznPG1yWCfIE5VfApQ6N+PLFX2b3k/qU3cZOCPDGpEm6xS P4ZxzXw0AnfwwmZYbz2kmhbp444Tb1y17sh52TdiewDxn7Ld5ftlA5rTVAvjNQW0MX0f Cq6w==
X-Gm-Message-State: AG10YORotMR27BIDmMzDZ7SlcsphaE7aN4dlNCtzT4oKwGChBTpdKGgaUB/rR1jEPYDeT6skCWjwfceQ4TCO22JDw+yn8Vno
X-Received: by 10.140.248.198 with SMTP id t189mr13270540qhc.42.1453406888159; Thu, 21 Jan 2016 12:08:08 -0800 (PST)
Received: from brn1lxmailout01.verisign.com (brn1lxmailout01.verisign.com. [72.13.63.41]) by smtp-relay.gmail.com with ESMTPS id y135sm444229qky.9.2016.01.21.12.08.07 (version=TLS1 cipher=AES128-SHA bits=128/128); Thu, 21 Jan 2016 12:08:08 -0800 (PST)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01 [10.173.152.205]) by brn1lxmailout01.verisign.com (8.13.8/8.13.8) with ESMTP id u0LK87UZ015927 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 21 Jan 2016 15:08:07 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Thu, 21 Jan 2016 15:08:02 -0500
From: "Gould, James" <JGould@verisign.com>
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>
Thread-Topic: [eppext] I-D Action: draft-lozano-ietf-eppext-registrar-expiration-date-00.txt
Thread-Index: AQHRVII5CddH1x7oPEyvfpfQ7AYzkZ8GX2rQgABaQAA=
Date: Thu, 21 Jan 2016 20:08:02 +0000
Message-ID: <3AFA41DD-C236-4E1E-92FB-BDF30BE8E94B@verisign.com>
References: <20160121193028.13313.82104.idtracker@ietfa.amsl.com> <831693C2CDA2E849A7D7A712B24E257F4A133A9D@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F4A133A9D@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: multipart/related; boundary="_004_3AFA41DDC2364E1E92FBBDF30BE8E94Bverisigncom_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/aliKARS9_X5SqpovzcOzLVHsBe8>
Cc: "eppext@ietf.org" <eppext@ietf.org>, Gustavo Lozano <gustavo.lozano@icann.org>
Subject: Re: [eppext] I-D Action: draft-lozano-ietf-eppext-registrar-expiration-date-00.txt
X-BeenThere: eppext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPPEXT <eppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eppext>, <mailto:eppext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eppext/>
List-Post: <mailto:eppext@ietf.org>
List-Help: <mailto:eppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eppext>, <mailto:eppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jan 2016 20:08:14 -0000

Gustavo,

I agree with Scott, it is not clear the relationship between the two and the relevance in the registry of maintaining this value.  Can the registrar expiration date be greater then the domain expiration date, less then the domain expiration date, or completely different from the domain expiration date?  The reference for the ThickWhoisPolicy is incorrect in the draft.  Please provide the appropriate reference and highlight where in the Thick Whois Policy it defines the requirement for the registry to hold and display a registrar expiration date in addition to the authoritative domain expiration date.

Thanks,


—


JG


[cid:77031CC3-BE7A-4188-A95F-D23115A30A4D@vcorp.ad.vrsn.com]

James Gould
Distinguished Engineer
jgould@Verisign.com

703-948-3271
12061 Bluemont Way
Reston, VA 20190

VerisignInc.com<http://VerisignInc.com>

On Jan 21, 2016, at 2:52 PM, Hollenbeck, Scott <shollenbeck@verisign.com<mailto:shollenbeck@verisign.com>> wrote:

-----Original Message-----
From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of
internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>
Sent: Thursday, January 21, 2016 2:30 PM
To: i-d-announce@ietf.org
Subject: I-D Action: draft-lozano-ietf-eppext-registrar-expiration-
date-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.


       Title           : Registrar Registration Expiration Date
Extension Mapping for the Extensible Provisioning Protocol (EPP)
       Author          : Gustavo Lozano
Filename        : draft-lozano-ietf-eppext-registrar-expiration-
date-00.txt
Pages           : 15
Date            : 2016-01-21

Abstract:
  This document describes an Extensible Provisioning Protocol (EPP)
  extension mapping for the provisioning and management of the
  registrar registration expiration date for domain names stored in a
  shared central repository.  Specified in XML, this mapping extends
  the EPP domain name mapping.

Gustavo, I wish this document would explain what this value actually means given that registrars are not the authoritative source of information for domain expiration dates. Could you please add some text to the Introduction that explains the purpose of the value and what it means of the context of the expiration date maintained by registries? Can they ever be different? What does it mean if they are different? Why are both needed if they are supposed to be the same?

I'd also like to suggest that you add text to the different command descriptions to make it clear what the values represent when you're extending a renew, transfer, etc.

Scott

_______________________________________________
EppExt mailing list
EppExt@ietf.org<mailto:EppExt@ietf.org>
https://www.ietf.org/mailman/listinfo/eppext

v2.23.0 | Report a Bug | By Email