Re: [eppext] Working Group Last call for draft-ietf-eppext-launchphase

"Hollenbeck, Scott" <shollenbeck@verisign.com> Tue, 21 July 2015 13:19 UTC

Return-Path: <shollenbeck@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 2F12D1B2AB4 for <eppext@ietfa.amsl.com>; Tue, 21 Jul 2015 06:19:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 Uugug02giF6S for <eppext@ietfa.amsl.com>; Tue, 21 Jul 2015 06:19:01 -0700 (PDT)
Received: from mail-qg0-f98.google.com (mail-qg0-f98.google.com [209.85.192.98]) (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 484A91ACF08 for <eppext@ietf.org>; Tue, 21 Jul 2015 06:19:01 -0700 (PDT)
Received: by qgal74 with SMTP id l74so6466929qga.2 for <eppext@ietf.org>; Tue, 21 Jul 2015 06:19:00 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:thread-topic:thread-index:date :message-id:references:in-reply-to:accept-language:content-language :content-type:content-transfer-encoding:mime-version; bh=hBQoW05Gf3fn98mSw9HvvcVzdh9GtNKPv1lfpkqPC80=; b=gOi0EOly6ybHS5jbHQEEaHUlhfeyN5g46kMEqnVNTzzN1M3FCg0v+G1x8lihUJ1mLK rMIZ9GFJrP3P+mDqFl+QcPbDSYkFiDjzy8tsq2u+PHdsJw1+9V/T2mKy20EQLfv3WxQY dyKs/CC96FhUHYIwZ3aqIDK+8I3BLYu3YdfOjk4kuJxDNuybjz3dLScGBrwAm83fd024 blzyLDYUOQ+zGqV5UK1hOTugYTsCYJW3CiSJP4hsgwaOoXVDyL+KPi49P1EjYKNnzzT8 KyeFUejnrNTAYFZsTrdUW29pjJaL3vo3Z5aGHyIXSBtJd+vER1O4Hp6BVpQ2PdaIfN8A Rl9g==
X-Gm-Message-State: ALoCoQmAtYwKZ3Z8/8ULyB+O4DeQtFMpDlOwDWELe33e5tTMKVycS4pN0DTYjA0nKRFzeeVWGjuF810LtQNWUMLihiK8HsC8sA==
X-Received: by 10.140.232.16 with SMTP id d16mr49885080qhc.14.1437484740540; Tue, 21 Jul 2015 06:19:00 -0700 (PDT)
Received: from brn1lxmailout02.verisign.com (brn1lxmailout02.verisign.com. [72.13.63.42]) by smtp-relay.gmail.com with ESMTPS id 1sm8008912qkx.1.2015.07.21.06.19.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 21 Jul 2015 06:19:00 -0700 (PDT)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02 [10.173.152.206]) by brn1lxmailout02.verisign.com (8.13.8/8.13.8) with ESMTP id t6LDIxAP026097 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 21 Jul 2015 09:18:59 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Tue, 21 Jul 2015 09:18:59 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: Antoin Verschuren <ietf@antoin.nl>, "eppext@ietf.org" <eppext@ietf.org>
Thread-Topic: [eppext] Working Group Last call for draft-ietf-eppext-launchphase
Thread-Index: AQHQw7PGnMgMW1gtVUqHy45bSVWUWp3l58IQ
Date: Tue, 21 Jul 2015 13:18:58 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F4A022D7F@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
References: <B785119F-67E7-4B34-9995-6A6F5806DF10@antoin.nl> <831693C2CDA2E849A7D7A712B24E257F4A022CD2@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F4A022CD2@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/4jJ09cScP_r0ZY71nzV6V881eEg>
Subject: Re: [eppext] Working Group Last call for draft-ietf-eppext-launchphase
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: Tue, 21 Jul 2015 13:19:03 -0000

> -----Original Message-----
> From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of Hollenbeck,
> Scott
> Sent: Tuesday, July 21, 2015 8:50 AM
> To: Antoin Verschuren; eppext@ietf.org
> Subject: Re: [eppext] Working Group Last call for draft-ietf-eppext-
> launchphase
> 
> > -----Original Message-----
> > From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of Antoin
> > Verschuren
> > Sent: Monday, July 20, 2015 4:02 PM
> > To: eppext@ietf.org
> > Subject: [eppext] Working Group Last call for draft-ietf-eppext-
> > launchphase
> >
> > Greetings,
> >
> > This is the starting of the WGLC on the Launch Phase Mapping for the
> > Extensible Provisioning Protocol (EPP).
> > There was extensive discussion on the mailing list, an we believe the
> > outcome is incorporated in the
> > document and is ready for WGLC.
> > The current version of this document can be found here:
> >
> >   https://www.ietf.org/id/draft-ietf-eppext-launchphase-05.txt
> 
> I have reviewed this document. Comments:
> 
> The URI for the "TMCH Functional Specification" appears twice in the
> list of URIs. One of the instances should be removed and the citations
> should be adjusted accordingly. More importantly, that URI identifies
> an expired Internet-Draft. Is it really the best reference? This isn't
> a normative reference so I don't think it needs to be brought up to
> date for this document to proceed, but I would like to ask if it makes
> sense to refer to expired I-Ds in this way.
> 
> Many of the examples in the document use domain names like
> "example1.tld". These names aren't consistent with RFC 6761.
> Consideration should be given to using 6761 domain names.
> 
> Could the authors please confirm that all of the examples are valid per
> the schema that appears in Section 4.1?

Sorry, one more comment: a template should be added to section 5 to register the XML schema in addition to the namespace. There's an example in RFC 5731.